konrad/NeitzelFXDesigner
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Generate typed Java ViewModels and discover declarative registry defaults

Browse Source
This commit is contained in:
konrad
2026-11-13 20:06:26 +01:00
parent adf432b98b
commit 8be0aec287
36 changed files with 1123 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/generated-model-metadata.md
+1 -1
View File
@@ -35,7 +35,7 @@ Build and Refresh already performs `clean package` in an isolated reactor copy.
## Boundaries and validation
This is build-time Model metadata for existing discovery and binding authoring. It does not generate Java ViewModel subclasses, a ViewModel registry, editable FXML forms, labels/control defaults, arbitrary BeanInfo metadata, Java source origins or project-wide Model selection UI. Those retain their later roadmap gates. The processor is a Java 21 build artifact depending only on the contracts; it is not packaged in either host or required on the application runtime path. Wire DTOs and protocol versions do not change.
This is build-time Model metadata for existing discovery and binding authoring. The subsequent [ViewModel generation slice](generated-viewmodels.md) now generates Java subclasses and registry defaults. Editable FXML forms, labels/control defaults, arbitrary BeanInfo metadata, Java source origins and a project-wide Model selection UI remain later work. Those retain their later roadmap gates. The processor is a Java 21 build artifact depending only on the contracts; it is not packaged in either host or required on the application runtime path. Wire DTOs and protocol versions do not change.
Automated tests compile real source with the processor, verify deterministic inherited/collection signatures and non-execution, clean-build removal, missing selections, schema bounds, generated/fallback equivalence, stale signatures and duplicate resources. Real classpath and module-path fixture processes require generated Person and nested Address metadata and retain their non-initialization assertions. The live shared-host scenario requires generated metadata provenance before handing discovery to the binding inspector, then runs existing source-preserving binding authoring and Undo/Redo tests in standalone and registered IntelliJ. No manual testing is requested; earlier skipped manual checks remain skipped.