Release v2.2.0 · RHarryH/avispa-ecm

Context match rule has to be provided as condition (not as a plain string)
Changes in expressions parsing - distinction between function and non-function context
Different dictionary configuration for combo boxes and radio buttons
Changed the way how properties are stored for easier apply of backend architecture changes
Changed the way how context resolving works due to changes in Hibernate 6

Property pages can define checkboxes
Context modes in property pages allowing for reuse of the same property page for readonly, insert and edit scenarios
conditions used to decide on the visibility of the property have been wrapped into new constraints section,
which allows to specify property requirement and modifiability rules
Extended conditions to support $like, $notLike, $limit and $orderBy operators (please note this is not supported by
the frontend implementetion of conditions)
Conditions can be now used not only for checking if something has matched but for
counting and fetching the results from the database
Redesigned combo boxes and radio buttons loading dynamic dictionaries by incorporating conditions
(this allows for example to limit the result)
Fixed tables - tables, which can't have rows added or deleted
Added possibility to make a full cleanup of the configuration

Better validation of type name when registered programmatically (type names are case-insensitive)
More detailed error messages in various places
Added possibility to register configuration types before specific configurations
Greatly improved EcmPropertyUtils reflection tools (for instance it supports nested properties)

Correct distinction between combo boxes and radio buttons when deserializing property page

Provide feedback