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.

Sign up for GitHub

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

Jump to bottom

Consistency in CQRS architecture package names #93

Closed
odrotbohm opened this issue Apr 28, 2023 · 0 comments
Closed

Consistency in CQRS architecture package names #93

odrotbohm opened this issue Apr 28, 2023 · 0 comments
Assignees
@odrotbohm
Labels
module: cqrs / es CQRS and Event Sourcing support type: enhancement New feature or request
Milestone
1.7

Comments

@odrotbohm
Copy link
Member

Contrary to all other architecture representations, the annotations to express CQRS stereotypes currently reside in cqrs.annotation. We should reintroduce them within cqrs itself and deprecate the legacy ones for removal in 2.0.
@odrotbohm odrotbohm added type: enhancement New feature or request module: cqrs / es CQRS and Event Sourcing support labels Apr 28, 2023
@odrotbohm odrotbohm added this to the 1.7 milestone Apr 28, 2023
@odrotbohm odrotbohm self-assigned this Apr 28, 2023
odrotbohm added a commit that referenced this issue Apr 28, 2023
@odrotbohm
GH-93 - Introduce CQRS annotations in cqrs package.
1845011 
Introduce a copy of the annotations currenly available in cqrs.annotation in the cqrs package. This is to create symmetry between all architectural jMolecules abstractions. The legacy annotations are deprecated for removal in 2.0 and annotated with the new ones in turn so that processing technology can look out for the new ones only and still find the legacy ones.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@odrotbohm odrotbohm

Labels
module: cqrs / es CQRS and Event Sourcing support type: enhancement New feature or request
Projects
None yet
Milestone
1.7
Development

No branches or pull requests
1 participant
@odrotbohm