Improve error handling and remove localStorage handling from the website #61
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
The localStorage should only be handled by the client script
I don't think we need this anymore?
|
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/laymonage/giscussions/2wokAqs8aLpiKCnRm86bWMRnGYw5 |
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.
The
localStoragehandling should only be handled by the client script during the<iframe>initialization. There's no point of handling it on giscussions' website. It would even trigger unexpected problems.Part of #39, but I'm sure there are still other places where we can improve the handling.