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
Right now, the type format validator and the cardinality validator of a class are instantiated directly by the corresponding Meta class of a pojo. This results in less configurable generated code (e.g., consumers cannot override the behaviour of some validators) and makes it hard to implement future enhancements which may require dependency injection such as supporting conditions on type aliases. (see #879)
I would propose to inject them in the same way as we currently inject conditions, i.e., using a ValidatorFactory argument.
Right now, the type format validator and the cardinality validator of a class are instantiated directly by the corresponding
Meta
class of a pojo. This results in less configurable generated code (e.g., consumers cannot override the behaviour of some validators) and makes it hard to implement future enhancements which may require dependency injection such as supporting conditions on type aliases. (see #879)I would propose to inject them in the same way as we currently inject conditions, i.e., using a
ValidatorFactory
argument.Below is an example from the CDM.
Current meta code for type
BondReference
:This would change to:
The text was updated successfully, but these errors were encountered: