-
### Use case
Using retainAll() for Set and Map targets will minimize the amount of add/remove operations required for these types.
This limits side effects of removing preemptively all elements th…
-
# OBJECT DAO, DTO, VO, ENTITY의 차이 | LGM1995
데이터를 다루기 위한 객체 VO, DTO, DAO, ENTITY의 차이
[https://lgm1995.github.io/posts/VO,DTO,DAO,ENTITY/](https://lgm1995.github.io/posts/VO,DTO,DAO,ENTITY/)
-
# Goal
The goal of this issue is to generate data type objects from the account-service OpenAPI spec.
# Acceptance Criteria
- [ ] Webhook Request and Response data types are generated from spec…
-
Hi @benkroeger, thanks for replying back to my issue about relations in #14 .
So I just tried your suggestion of adding in the annotated relations, but I am now running into more issues. The `crea…
-
**Description:**
Currently, the serialization of `Quantity` objects in the library always displays the unit based on its class, as defined by the custom `SystemOfUnits`. This can be limiting an…
-
### Description
Add calculated fields for `/v2/process-instances/search` endpoint. Part of https://github.com/camunda/camunda/issues/20660
More specifically, the following limitation must be…
-
Shouldn't we convert datastructure (aka entity) into another kind of DTO at the transition between service (aka usecase) and repository(aka gateway)? After all, the rules of interaction between busine…
-
-
-
Where are your DTO to DAO conversions?
I don't see a util package where you are converting you internal entity to a DTO