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
Mandatory Inputs and Dependencies are dangerous.
They can cause who vajrams to fail (that is the meaning of mandatory). Also adding a new mandatory input breaks backward compatibility.
Today when we add a input/dependency to a vajram, it assumed as mandatory by default unless the developer marks the type of the facet field as Optional<T>. This is dangerous. All facets must be optional unless the developer deliberately marks it as mandatory.
To support, remove support for Optional<> in facets, and provide a @Mandatory annotation which MUST be added to mandatory facets. If this annotation is missing, then the facet is assumed to be Optional
The text was updated successfully, but these errors were encountered:
RamAnvesh
changed the title
#ExplicitMandatory Make inputs and dependencies mandatory only if @Mandatiry annotation is set on the facet.
#ExplicitMandatory Make inputs and dependencies mandatory only if @Mandatory annotation is set on the facet.
Jul 9, 2024
Mandatory Inputs and Dependencies are dangerous.
They can cause who vajrams to fail (that is the meaning of mandatory). Also adding a new mandatory input breaks backward compatibility.
Today when we add a input/dependency to a vajram, it assumed as mandatory by default unless the developer marks the type of the facet field as
Optional<T>
. This is dangerous. All facets must be optional unless the developer deliberately marks it as mandatory.To support, remove support for
Optional<>
in facets, and provide a@Mandatory
annotation which MUST be added to mandatory facets. If this annotation is missing, then the facet is assumed to be OptionalThe text was updated successfully, but these errors were encountered: