Skip to content
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

"hidden" property ui option #19

Open
romancow opened this issue Oct 4, 2023 · 0 comments
Open

"hidden" property ui option #19

romancow opened this issue Oct 4, 2023 · 0 comments
Assignees

Comments

@romancow
Copy link
Collaborator

romancow commented Oct 4, 2023

There could be a case to add a "hidden" ui option, such as her with the extra "male" object select:
genderunselected

Though considering there are cases we would want to be able to enable/disable empty object like this, how would this ui option be determined when webgme-taxonomy json schema is being created?

Also, it may not be necessary in this case since this property probably should be set to required, and then we can just hide required empty objects (since it has to be in the data and there are no settings for it). So then the question are there other cases for a "hidden" ui option? If it's not an empty object, it would seem necessary to show it to select the value(s), else what's the point of it being there?

@romancow romancow self-assigned this Oct 4, 2023
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

No branches or pull requests

1 participant