Skip to content

Project Custom Properties tab and ability to create properties#1550

Open
ktuite wants to merge 1 commit into
masterfrom
ktuite/custom_properties
Open

Project Custom Properties tab and ability to create properties#1550
ktuite wants to merge 1 commit into
masterfrom
ktuite/custom_properties

Conversation

@ktuite
Copy link
Copy Markdown
Member

@ktuite ktuite commented May 13, 2026

Closes getodk/central#1870

Screenshot 2026-05-13 at 4 02 28 PM

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:

  • run npm run test and npm run lint and confirmed all checks still pass OR confirm CircleCI build passes
  • verified that any code or assets from external sources are properly credited in comments or that everything is internally sourced

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Project-level "Custom Properties" tab with user properties management screen

1 participant