-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature Request: Support Generation from Domain Models #173
Comments
It generates output based on the Here is an example For now not every aspect is working but you can try |
The solution with JSON
is not scalable cause it falls apart in complex cases due to the lack of static analysys |
Fantastic! Thanks for the quick reply. I realised that a lot of the functionality I was looking for was also available by writing named constructors on the model 😊 |
Hi @etegan! Please check our reactive_forms_widget package We would appreciate sponsorship subscription or one time donation |
Hello again. I noticed what I think might be a bug. The named constructor approach that I mentioned together with the @RfArray annotations results in a UserForm without the add* methods
|
Solved: the named constructor can not be the first constructor. This works:
|
Hi @etegan! Please check our reactive_forms_widget package We would appreciate sponsorship subscription or one time donation |
Leaving it open if you still want to classify it as a bug :) |
Hello and first of: Thanks for these great packages!
Problem Statement
Currently, the generator requires models with nullable fields to represent form state, forcing developers to maintain two parallel models:
This leads to unnecessary duplication and makes it harder to maintain type safety between form submissions and domain objects.
Example of current approach:
Proposed Enhancement
The generator should automatically generate both:
The
@Rf
annotation should support configuring partial data injection through related models.Example Usage
Benefits
Implementation Notes
The generator would need to:
@Rf
annotation for partial data configurationWould you consider this enhancement for a future release? It would significantly improve the developer experience when working with domain-driven architectures.
The text was updated successfully, but these errors were encountered: