Snappy Fix - Locations Component #203
Merged
Conversation
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
👋 Thanks for opening a pull request!If you are new, please check out the trimmed down summary of the deployment process below:
If you have a larger change and want to block deployments, you can run
|
This was referenced Aug 5, 2023
|
.deploy |
Deployment Triggered 🚀GrantBirki, started a branch deployment to github-pages You can watch the progress here 🔗
|
Deployment Results ✅GrantBirki successfully deployed branch |
This was referenced Aug 5, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Snappy Fix
This pull request removes the locations component from the main page since it is "jumpy". I am not sure why, but when scrolling around the
locationscomponent, (only downwards) it causes the page to jump farther down like someone bumped your scroll bar. By putting thelocationscomponent on its own page, this is no longer an issue.