You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The studio team has had trouble explaining why some fields needs to be set while creating a UI for configuring payment.
Specifically the field "dataModel" in layout-sets.json should at least be optional, since you in most cases will not use any data from a datamodel directly in you layout. This property is per now required in order to avoid crashing the app.
Additional Information
The property was first introduced for payment as a result of re-using the config and process handling from the data-task.
Tasks
No response
Acceptance Criterias
No response
The text was updated successfully, but these errors were encountered:
Magnusrm
added
the
status/draft
Status: When you create an issue before you have enough info to properly describe the issue.
label
Aug 19, 2024
Description
The studio team has had trouble explaining why some fields needs to be set while creating a UI for configuring payment.
Specifically the field "dataModel" in layout-sets.json should at least be optional, since you in most cases will not use any data from a datamodel directly in you layout. This property is per now required in order to avoid crashing the app.
Additional Information
The property was first introduced for payment as a result of re-using the config and process handling from the data-task.
Tasks
No response
Acceptance Criterias
No response
The text was updated successfully, but these errors were encountered: