Project Custom Properties tab and ability to create properties#1550
Open
ktuite wants to merge 1 commit into
Open
Project Custom Properties tab and ability to create properties#1550ktuite wants to merge 1 commit into
ktuite wants to merge 1 commit into
Conversation
This file contains hidden or 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.
Closes getodk/central#1870
What has been done to verify that this works as intended?
I've used it along with the backend in getodk/central-backend#1824
I haven't written tests for it yet, though.
Why is this the best possible solution? Were any other approaches considered?
We've discussed a lot of ways to show user properties, and this was the one we decided to start with!
How does this change affect users? Describe intentional changes to behavior and behavior that could have accidentally been affected by code changes. In other words, what are the regression risks?
This is part of a larger effort to give more flexibility and enable entity segmentation.
Does this change require updates to user documentation? If so, please file an issue here and include the link below.
We will want to add user documentation about what these properties are and how to use them.
Before submitting this PR, please make sure you have:
npm run testandnpm run lintand confirmed all checks still pass OR confirm CircleCI build passes