v1.6.0: Dry Run Validation, Sorting, and GitHub Workflow Generation

Version 1.6.0 improves validation and project usability, adds entity-level sorting support, introduces basic GitHub Actions workflow generation, and fixes a mapper generation issue that could cause compilation errors.

What's new

• Added dry run validation for CRUD specs
  A new dry run validator has been introduced to make it easier to verify whether a CRUD spec file is valid before generation.

• Added dependency check as part of dry run validation
  The validator can now also check whether the target pom.xml contains the dependencies required by the provided CRUD spec configuration.

• Added entity-level sorting support
  You can now configure basic sorting per entity using:

sort:
  allowedFields: [name, price, releaseDate]
  defaultDirection: ASC

This enables generated resources to support controlled sorting while ensuring that only explicitly allowed fields can be used.

• Added basic GitHub Actions workflow generation
  A new additional property is now available for generating a base GitHub workflow:

  • github.actions

  This helps bootstrap CI setup for generated projects.

• Improved README and project documentation
  The README has been updated to be more readable and easier to follow.

• Added demo video and demo CRUD spec to the documentation
  The project now includes a demo video and the CRUD spec used in that demo, making it easier to understand the generator workflow end to end.

• Fixed mapper generation issue for eager-only mappings
  A bug was fixed where generated mappers could miss the required mapping annotation import when only eager fields were present. In such cases, the generated code could fail to compile.

Validation improvements

Validation has been extended beyond spec structure checks.

The new dry run validator now helps detect two common problems earlier:

• invalid or incomplete CRUD spec definitions
• missing required dependencies in pom.xml

This makes it easier to catch configuration issues before generation or compilation.

Upgrade note

If you are upgrading from an earlier version, review your project setup if you plan to use dry run validation or entity sorting.

In particular:

• sorting must be explicitly configured per entity
• dependency checks rely on the target pom.xml
• GitHub workflow generation is available through the github.actions additional property