feat: allows users to override inaccurate planning constraints #3216
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.
Begins to incorporate design feedback from call, replaces #3201 (links to a filtered, centered Planning Data map instead of rendering our own per constraint).
Lots of new questions! So many links & actions to contend with inside of accordions.
Outstanding tasks here if someone else picks up before 27 June:
onSubmit
_constraints
passport var to reflect "original"/"auditable" Planning Data response (this does not power future automations)property.constraints.planning
and added to_nots: { property.constraints.planning... }
(unless granular A4)property.constraints.planning
&_nots
should stay the same (unless granular A4)_overrides: { property.constraints.planning... }
to record the specific Planning Data entity IDs that were overridenproperty.type
orproperty.constraints.planning
)