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.
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
chore: add analytics tracking to capture
PlanningConstraints
&PropertyInformation
"overrides" #3510chore: add analytics tracking to capture
PlanningConstraints
&PropertyInformation
"overrides" #3510Changes from 4 commits
9eb8035
4401801
73ac292
961ec07
c75bf35
a9655fc
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
Check warning on line 129 in api.planx.uk/modules/gis/service/classifiedRoads.ts
GitHub Actions / Run API Tests
Check warning on line 151 in api.planx.uk/modules/gis/service/classifiedRoads.ts
GitHub Actions / Run API Tests
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.
An observation / pattern I didn't really notice last time round when
inaccurateConstraints
were added to this component.This component has transitioned from being informational only, to now capturing data much like other components. This data is generally captured and validated using formik (unlike the
useState()
hook here forinaccurateConstraints
).This particular function is essentially handling the "back" behaviour usually managed by
getPreviouslySubmittedData()
.If / when we come back to handle using formik for the
OverrideEntitiesModal
instances, it likely makes sense that this state would live at this root component level to match the behaviour of other components as opposed to individual instances within each modal as I think I'd previously suggested.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.
Thanks for noting this here so we have record when coming back; will leave unresolved so stays expanded 👍