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
feat: editors can select which planning constraints to check #3968
feat: editors can select which planning constraints to check #3968
Changes from 4 commits
51c7c57
99bea39
ea49acb
ec1c451
b575d1d
4147b44
65e699e
fefc6a9
c63941f
edcfd70
5741b31
48f3b6a
bb8b36e
fa8e206
8fdf00f
5dc3813
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Maybe
datasets
is more meaningful here?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.
Do we need a fallback way of handling "all" values?
If Planning Data add a new dataset, it would be pretty cumbersome to have to get all services to toggle it on. I think Editors would think that ticking the "main" checkbox means "all datasets" not just "all currently listed".
Alternatively if we could easily update all
PlanningConstraints
nodes with any new dataset this would also be solved.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.
Feel quite strongly that
datasets
is NOT a good name because we're not allowing users to say "I only want to check TPO orders dataset from Planning Data, not TPO zones" - rather we're letting them select/deselect our pre-curated "options" (each with a title, passport value, and associated source datasets).Perhaps
options
is more generic and easier to grasp here though? In my mind, they're basically the PlanningConstraint node's equivalent of Question/Checklist "edges"/"options" ?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.
As for the "all" question - I think this becomes much simpler in a word of Templates (eg PlanningConstraints will not be a "placeholder" node therefore just updated once per service template & changes propagated to children on publish?), and if still too cumbersome then would favor data migration script like you say!
Also no near-future requests for more datasets from Planning Data besides Planning History which I think will have a strong argument for it's own component or API outside of existing
/gis
.