Overview of the feature request
Value object are really useful to keep code clean and maintainable.
This feature request proposes the implementation @valueObject(cascade).
- A cascade all entity is not a real value object, because it has identity, but the implementation is related that's why IMO we should implement it as
@valueObject(cascade).
Once implemented we could add others value objects implementations:
@valueObject(embedded) using @Embbeded annotation. (There is already a @Embedded implementation for backend-only and cassandra database).
@valueObject(json) converting the object into a json string when persisting, (use jsonp type in postgres).
Scope of this feature request:
@valueObject(cascade) backend implementation.
- angular frontend implementation.
- cypress for value object forms will be kept out for now.
Cascade implementation:
- Cascade removes backend apis related to list/find while value objects should remove every backend api specific to the object.
Motivation for or Use Case
Related issues or PR
Overview of the feature request
Value object are really useful to keep code clean and maintainable.
This feature request proposes the implementation
@valueObject(cascade).@valueObject(cascade).Once implemented we could add others value objects implementations:
@valueObject(embedded)using@Embbededannotation. (There is already a@Embeddedimplementation for backend-only and cassandra database).@valueObject(json)converting the object into a json string when persisting, (use jsonp type in postgres).Scope of this feature request:
@valueObject(cascade)backend implementation.Cascade implementation:
Motivation for or Use Case
Related issues or PR