schema-generated forms support UISchema #987
Labels
No labels
ambition
application-offering
ambition
configure-applications
ambition
front-end
ambition/install-applications
ambition
security
ambition
switch-host
ambition
update-applications
ambition
user-management
blocked
component
api-service
component
fediversity-panel
component
nixops4
documentation
points
0
points
0.5
points
1
points
13
points
2
points
21
points
3
points
34
points
5
points
55
points
8
points
infinite
productisation
project-management
question
role
application-developer
role
application-operator
role
hosting-provider
role
maintainer
security
technical debt
testing
type
bug
type
deliverable
type
key-result
type
objective
type
task
type
unclear
type
user-story
user experience
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Blocks
#628 render option forms
fediversity/fediversity
Reference
fediversity/fediversity#987
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
As an operator,
I want for forms to render form elements appropriately,
so that e.g. credentials may stay confidential.
implementation notes
UISchemaoffers this by e.g.:json-schema-form-elementreact-jsonschema-formactually, while
react-jsonschema-formhandled passwords by itsUISchemaat the time, the JSON-Schema spec now has at least:format(respected by JSONForms', in this case for valuepassword)writeOnlynow, for in as far as we could do with just generated JSON-Schema, that might actually be preferable, in the sense that having to keep a manually curated VCS-tracked
UISchemaseems a headache - tho even if for just OEM white-labeling (#1029), it would seem nice.(prior to the switch to JSONForms, this was tracked at #520.)
do we even need passwords in the form tho for now? see also #190 (comment)
closing as unactionable / out of scope for MVP