Navbar component

[BrianSpencerDev]

The navbar should be one of the first components built due to its use across the web app.

While logged in the navbar should

• have a search bar in the middle
• a profile icon on the top right

while logged out

• no search bar
• a sign up/sign in button instead of profile icon

[madCakes]

I'll get on this

[madCakes]

still a complete noob. Do i make a pull request for the main brain and go from there? Never worked with other devs before so still wobbly on this stuff

[BrianSpencerDev]

No worries. Make a branch from the development branch named something like feature/navbar then go from there. When done make a pull request so we can merge your branch with the development branch

[madCakes]

still a bit lost mate, do i clone the repo and make a branch from there?

Only thing I could see in the clone was the readme from the first commit

[BrianSpencerDev]

Right you clone the repo so you can have a local repo on your machine. You are only seeing the readme file is because you are seeing the main branch.

you can go to different branches by:

git checkout (branch name here)

so to make a branch from the development branch you would do

git checkout development git checkout -b feature/navbar (this will create a new branch named feature/navbar and will take you to that branch once it created)

you then do your work on the new branch

[madCakes]

Im being a real baby dev right now. I got this:

fatal: not a git repository (or any of the parent directories): .git

edit figured it out

[madCakes]

I have to push to the new branch before a pull request right?

I apparently don't have permission to push? also wasn't able to set upstream either, so I'm sure I'm missing something.

Edit: wanted to get the pull request all sorted before I began working on it. I'll be able to focus on the project over weekend and hopefully catch up by then. I'm just slow to start lool

[BrianSpencerDev]

That's on me sorry. Thought you being a member of our organization would give you write access by default. I changed it and you should be good to go

[madCakes]

I'm full of issues today. npm start is giving me errors:

PS C:\Users\Jb328\OneDrive\Desktop\CODING\Projects\Hackathon\Hackathon1\clerk-hashnode-hackathon-app> npm start npm ERR! code ENOENT npm ERR! syscall open npm ERR! path C:\Users\Jb328\OneDrive\Desktop\CODING\Projects\Hackathon\Hackathon1\clerk-hashnode-hackathon-app\package.json npm ERR! errno -4058 npm ERR! enoent ENOENT: no such file or directory, open 'C:\Users\Jb328\OneDrive\Desktop\CODING\Projects\Hackathon\Hackathon1\clerk-hashnode-hackathon-app\package.json' npm ERR! enoent This is related to npm not being able to find a file. npm ERR! enoent

npm ERR! A complete log of this run can be found in: npm ERR! C:\Users\Jb328\AppData\Roaming\npm-cache_logs\2021-07-23T17_09_24_871Z-debug.log

---

I ran 'npm i' before and got this:

npm WARN saveError ENOENT: no such file or directory, open 'C:\Users\Jb328\OneDrive\Desktop\CODING\Projects\Hackathon\Hackathon1\clerk-hashnode-hackathon-app\package.json'
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN enoent ENOENT: no such file or directory, open 'C:\Users\Jb328\OneDrive\Desktop\CODING\Projects\Hackathon\Hackathon1\clerk-hashnode-hackathon-app\package.json'
npm WARN clerk-hashnode-hackathon-app No description npm WARN clerk-hashnode-hackathon-app No README data npm WARN clerk-hashnode-hackathon-app No license field.

up to date in 0.446s found 0 vulnerabilities

---

(Unsure how relevant that is )

Been looking around online for solutions but haven't come across anything solid yet.

[BrianSpencerDev]

Try running npm i and npm start inside the client folder

[madCakes]

Absolute lifesaver

[madCakes]

My health has been poor lately so I'm more behind than I expected. I should be able to get the nav done by today/tomorrow and finish up the design I hope