[
https://issues.apache.org/jira/browse/CAUSEWAY-3624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andi Huber resolved CAUSEWAY-3624.
----------------------------------
Resolution: Resolved
Resolved by giving facets Property.Required and Parameter.Required (higher)
prio over others. (Changing the Parameter logic, would not have been strictly
required. However, this is for symmetry.)
> Allow MANDATORY Property/Parameter to be set even if backends are more
> relaxed.
> -------------------------------------------------------------------------------
>
> Key: CAUSEWAY-3624
> URL: https://issues.apache.org/jira/browse/CAUSEWAY-3624
> Project: Causeway
> Issue Type: Improvement
> Components: Core
> Reporter: Andi Huber
> Assignee: Andi Huber
> Priority: Major
> Fix For: 2.0.0-RC4
>
>
> Its a valid use case to have a database column null-able, however enforce a
> non-null value in the UI.
> Particularly important, if a column is mapped to an enum, where a null value
> in the column maps to a specific enum constant like NONE or NO say.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
