-
Notifications
You must be signed in to change notification settings - Fork 33
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
Add Home link placement in the header for better accessibility #76
Merged
Merged
Changes from 5 commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
e3dec1b
add Home link to header for easy navigation to first page
Chirag-S-Kotian 10917bc
Add Home link placement in the header for better accessibility
Chirag-S-Kotian 5b2389a
Updated link UX in PageContainer
Chirag-S-Kotian fd7d25a
fixed prettier problem
Chirag-S-Kotian 6372c32
apply Prettier to fix code formatting issues
Chirag-S-Kotian d8f502e
removed yarn.lock and package-lock.json files and updated package.jso…
Chirag-S-Kotian 6dc40dc
"Updated version specifiers in package.json"
Chirag-S-Kotian 48deec6
updated yarn.lock file
Chirag-S-Kotian 69d338c
Updated yarn.lock file with yarn command
Chirag-S-Kotian File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
There is no need to update these versions.
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.
Could you please tell me how to remove package.json and yarn.lock , should I delete from my repo?
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.
Hey!
You can delete the
package-lock.json
file from your repo.Regarding the
yarn.lock
file, if you keep the current versions of all the packages, everything should be fine and you won't need to remove this file. To keep the current versions of all the packages you need to have this:"@semaphore-protocol/data": "4.3.1"
instead of this:"@semaphore-protocol/data": "^4.4.1"
and"next": "14.1.0"
instead of"next": "^14.2.15"
in thepackage.json
file.Please let me know if you have any other questions.
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.
okay i removed both and updated package.json file
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.
Hey! Great! Thank you! Please, could you create an empty
yarn.lock
file in the root of the project and run the commandyarn
and push the changes? Theyarn.lock
file should still be in the repo but this PR shouldn't modify it.After that, I think the PR is ready.
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.
i did it anyway and pushed same yarn.lock which is present in boilerplate repo
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.
Hey! The new
yarn.lock
file is almost correct. If you runyarn
, it will be updated and you can push the change. The change will be just adding a line at the end of the file.The
yarn.lock
file should not be part of these files after you push the change: https://github.com/semaphore-protocol/boilerplate/pull/76/filesRight now it's there: https://github.com/semaphore-protocol/boilerplate/pull/76/files#diff-51e4f558fae534656963876761c95b83b6ef5da5103c4adef6768219ed76c2de
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.
okay changes are complete.