chore: update DrawBoundary upload key from proposal.drawing.locationPlan to locationPlan
#2758
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
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.
This one isn't exposed as editor props, so it'll be live across services as soon as it's merged ! We'll coordinate merge with other file key changes.
Related to theopensystemslab/planx-core#289 & theopensystemslab/planx-data-migrations#7
BOPS logic is repeated in the editor's
Sendcomponent still for frontend CSV generation - I'll take a look at properly refactoring using the planx-core public client today so we don't have to repeat the same find-and-replace across the v1 tagging functions.