Skip to content
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

Support jmolecule annotations on generated code - first step #141

Open
jangalinski opened this issue Sep 7, 2024 · 1 comment
Open

Support jmolecule annotations on generated code - first step #141

jangalinski opened this issue Sep 7, 2024 · 1 comment
Assignees
Labels
Prio: SHOULD Feature is essential for the next release Status: in progress Type: enhancement New feature or request
Milestone

Comments

@jangalinski
Copy link
Contributor

jmolecules defines a vocabulary as annotations that allow us to mark code as DDD/CQRS behavior.

Examples: data classes that define commands or events should be marked with the Command or DomainEvent annotations, command handlers that accept a command and publish an event should be marked with DomainEventPublisher and CommandHandler, ...

This feature needs to be optional, so if the app using the code generator does not define dependencies on jmolecules, the code should not be added, so we do not get unwanted compile errors and force apps to use jmolecules when they do not want to.

Scope

The first implementation should provide AnnotationSpec abstractions for the relevant jmolecules annotations and processors to enhance generated specs where applicable.

A processor must be added that supports Command and DomainEvent.

@jangalinski jangalinski self-assigned this Sep 7, 2024
@jangalinski jangalinski added this to the 0.0.1 - MVP milestone Sep 7, 2024
@jangalinski jangalinski added Prio: SHOULD Feature is essential for the next release Status: in progress Type: enhancement New feature or request labels Sep 7, 2024
@jangalinski
Copy link
Contributor Author

see #142

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Prio: SHOULD Feature is essential for the next release Status: in progress Type: enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant