As a VFS developer, I need to the forms library to direct support read-only data, so that I can avoid inconsistent workarounds involving empty schemas and empty objects.
Additional details/notes/links
Read-only data is only pseudo supported, with a variety of ways that teams have gotten around this, (empty schemas, empty objects) but a consistent way to deal with this would be good. A good example is read-only demographic information. The current "View-only data" support is view only in the sense that it only appears client side, but still editable.
Ideally, we should be able to have a read-only data field. The data should be able to be loaded from a data source (API call), a calculation based on another field, or a static value (I do not that that is as useful).
Currently, teams have used a combo 'view:fieldName', a custom component that is tied to redux, empty schemas and/or hiding the header row on the review page.
It might look something like
properties: {
'claimInfo': {
type: 'object',
properties: {
claimId: {
type: 'string',
data:async (formData) => {
// load data for text field here
}
},
},
},
},
What would the form config look like for this read-only data? I agree that the current support is kind of hacky, but I don't have any ideas for alternatives.
User story
As a VFS developer, I need to the forms library to direct support read-only data, so that I can avoid inconsistent workarounds involving empty schemas and empty objects.
Additional details/notes/links
Read-only data is only pseudo supported, with a variety of ways that teams have gotten around this, (empty schemas, empty objects) but a consistent way to deal with this would be good. A good example is read-only demographic information. The current "View-only data" support is view only in the sense that it only appears client side, but still editable.
Ideally, we should be able to have a read-only data field. The data should be able to be loaded from a data source (API call), a calculation based on another field, or a static value (I do not that that is as useful).
Currently, teams have used a combo 'view:fieldName', a custom component that is tied to redux, empty schemas and/or hiding the header row on the review page.
It might look something like
Acceptance criteria
TBD
Point(s) of contact
@mdewey
What type of issue is this?
How to configure this issue