fix: Apply auth to public upload, not private #2427
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
jessicamcinchak
approved these changes
Nov 15, 2023
I know right - no apologies needed - a quirky language thing where public upload is private, and private is public 🙃 |
|
Removed vultr server and associated DNS entries |
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.
What's the problem?
Reported here on ODP Slack - https://opendigitalplanning.slack.com/archives/C0241GWFG4B/p1700064607120349
Uploading files is not working from applicant facing flows.
What's the solution?
The route guard
useTeamEditorAuth()was incorrectly applied to the "public" and not the "private" - anybody can upload to private, only Editors can upload to public 🙃Maybe another sign that some E2E file upload tests may be a good idea to consider soon?