-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Taha's Code Review #45
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Love the project, nice idea and very well-executed.
The code is super easy to read, all the components are named very clearly and the folder structure makes sense. You've even got an underscore before your _lib folder, nice.q
In a page.js file I'm generally expecting it to be a server component that does some data fetching and returns a stack of semantically-named components. This helps a developer that's new to the project to be able to tell at a glance what the page is and what it does. You've done that really nicely here:
...but it's less clear on other pages. Not a big deal at all, and definitely something that could fall by the wayside when you're working at the pace you guys have to. I'd reccomend turning more of the HTML into components to enhance readability.
Very impressed that you got some tests out, well done to the QA for finding time to do that.
I also like the random image on the homepage, great feature
Looks like you're using some legacy props for the Image component and that's causing some console errors. You're also doing some data-fetching in a funky place on the homepage. I might do something like this instead:
Something you'll see a lot in larger codebases that you don't necessarily need to worry about for now is something like this:
The text was updated successfully, but these errors were encountered: