-
Notifications
You must be signed in to change notification settings - Fork 7
Hadidreem17 w2 react #20
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
base: main
Are you sure you want to change the base?
Hadidreem17 w2 react #20
Conversation
Bumps [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite) from 5.2.11 to 5.4.6. - [Release notes](https://github.com/vitejs/vite/releases) - [Changelog](https://github.com/vitejs/vite/blob/v5.4.6/packages/vite/CHANGELOG.md) - [Commits](https://github.com/vitejs/vite/commits/v5.4.6/packages/vite) --- updated-dependencies: - dependency-name: vite dependency-type: direct:development ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [braces](https://github.com/micromatch/braces) from 3.0.2 to 3.0.3. - [Changelog](https://github.com/micromatch/braces/blob/master/CHANGELOG.md) - [Commits](micromatch/braces@3.0.2...3.0.3) --- updated-dependencies: - dependency-name: braces dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
robvk
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good project, but everything surrounding the actual code is not ok:
- Missing link to the deployed version
- You have week1 code in the PR. There were issues with this last week too, be more aware of what you files you are adding to a PR
Please add a link to the deployed version.
If I see week1 and week2 in your PR next week I will request you to fix it. It is not fun to do so really make sure you are doing it correctly. Whenever you are starting a new branch make sure to checkout main first. When you start a branch it will take your current position as the start. If you do that from your week 2 branch it will then see all those changes as something to add again.
| } catch (err) { | ||
| setError(err.message); | ||
| } finally { | ||
| setLoadingProducts(false); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great use of finally
| <button | ||
| type="button" | ||
| className="back-button" | ||
| onClick={() => navigate(-1)} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice use of the navigate hook!
|
Deployed version: https://papaya-starburst-78c17d.netlify.app/ |
No description provided.