schema-generated forms support UISchema #987

Closed
opened 2026-05-20 09:19:07 +02:00 by kiara · 3 comments
Owner

As an operator,
I want for forms to render form elements appropriately,
so that e.g. credentials may stay confidential.

implementation notes

  • UISchema offers this by e.g.:
  • needs migration on updates, see #159
  • seems tightly coupled with code-base version, whereas we cannot generate this (beyond e.g. converting to JSON), so we may need to store this in version control
    • having JSON generated seems possible, and would need to be calculated just like the main schema, tho we may need to check if this is worth it
**As** an operator, **I want** for forms to render form elements appropriately, **so that** e.g. credentials may stay confidential. ### implementation notes - [x] `UISchema` offers this by e.g.: - [`json-schema-form-element`](https://jsfe.js.org/Sink/UiSchemas) - [`react-jsonschema-form`](https://github.com/rjsf-team/react-jsonschema-form) - [conditional display](https://github.com/rjsf-team/react-jsonschema-form/blob/main/packages/docs/docs/json-schema/dependencies.md#conditional) - **[JSONForms](https://github.com/eclipsesource/jsonforms)** - needs migration on updates, see #159 - seems tightly coupled with code-base version, whereas we cannot generate this (beyond e.g. converting to JSON), so we may need to store this in version control - having JSON generated seems possible, and would need to be calculated just like the main schema, tho we may need to check if this is worth it
Author
Owner

actually, while react-jsonschema-form handled passwords by its UISchema at the time, the JSON-Schema spec now has at least:

  • format (respected by JSONForms', in this case for value password)
  • writeOnly

now, 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 UISchema seems 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.)

actually, while `react-jsonschema-form` handled passwords by its `UISchema` at the time, the JSON-Schema spec now has at least: - [`format`](https://json-schema.org/draft/2020-12/draft-bhutton-json-schema-validation-00#format) (respected by JSONForms', in this case for value `password`) - [`writeOnly`](https://json-schema.org/draft/2020-12/draft-bhutton-json-schema-validation-00#rfc.section.9.4) now, 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 `UISchema` seems 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.)
Author
Owner

do we even need passwords in the form tho for now? see also #190 (comment)

do we even need passwords in the form tho for now? see also https://git.fediversity.eu/fediversity/fediversity/issues/190#issuecomment-5327
Author
Owner

closing as unactionable / out of scope for MVP

closing as unactionable / out of scope for MVP
kiara closed this issue 2026-06-06 16:19:20 +02:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Blocks
#628 render option forms
fediversity/fediversity
Reference
fediversity/fediversity#987
No description provided.