-
Story
-
Resolution: Done
-
Major
-
0.14.0
-
None
-
8
-
2020 Week 49-51 (from Nov 30), 2021 Week 04-06 (from Jan 25), 2021 Week 07-09 (from Feb 15), 2021 Week 10-12 (from Mar 8)
Part 2 – follow up to KOGITO-1649
As a developer, I want to know how kogito-codegen works and how to extend it with custom components.
- validation phase (e.g. sort of symbol table where you collect names and types)
- error reporting (fatal error stops codegen or recoverable error – continues)
- customizing code gen
- registering addons (with custom codegen)
e.g. consider using BuildStep like in Quarkus? etc...
- incorporates
-
KOGITO-2929 ProjectRuntime: remove for non-legacy use cases
- Resolved
-
KOGITO-2911 Refactor Codegen for "RuleUnits" class in Application.java
- Resolved
-
KOGITO-2918 ApplicationSections should be self-contained generators
- Closed
-
KOGITO-2931 Avoid code duplication for template selection
- Closed
-
KOGITO-1826 Standardize check for injection enabled in Generator classes
- Closed
- is blocked by
-
KOGITO-3969 Review ApplicationGenerator.logger usages
- Resolved
-
KOGITO-3972 Make TemplateGenerator use KogitoBuildContext
- Resolved
-
KOGITO-3974 Make DecisionModels and PredictionModels injectable
- Resolved
-
KOGITO-3975 Refactor Application and Config API to make them easier to extend
- Resolved
-
KOGITO-4012 KogitoBuildContext refactoring
- Resolved
-
KOGITO-4073 Remove Files.write from generators
- Resolved
-
KOGITO-4105 Refactor Application configs generation/wiring to make them generic
- Resolved
-
KOGITO-3995 Rename ApplicationGenerator.withGenerator to improve readability
- Resolved
-
KOGITO-2901 Review GeneratedFile.Type classification
- Closed
- relates to
-
KOGITO-1649 Restructure codegen to make it extensible and cleaner (Part 1)
- Resolved