Sebastien Pelletier

Static helper methods make the api really nice and compact for default usage when we don't have to override too many configs (e.g. custom ID collection factory, results collection factory,...

If the POJOs returned from the different method calls to be assembled declare JPA annotation e.g. `@Id`, `@OneToOne`, etc., it would be nice to honor those, this would allow to...

A lot of copy/paste tests reside between modules (e.g. _assembler_, _assembler-cache-caffeine_, _assembler-spring-cache_) + copy/paste test patterns within same modules. Common test code/patterns should be regrouped, and advanced functionalities such as...

Currently the Assembler reactive and non-blocking support is backed by Project Reactor. We expose the `Flux` type and internally leverage Project Reactor api with `Flux` and `Mono`. Exposing different reactive...

By having `cached()` functions implement `RuleMapper` instead of `RuleMapperSource`, we avoid the additional step of flattening the cache before processing it as a stream in `oneToOne()` and `oneToMany()` functions

The goal is to provide a default implementation of `Cache` per module/dependency (e.g. Caffeine cache, Spring cache, etc.). This would allow, if e.g. assembler-cache-caffeine is present in the classpath, to...

Expose metrics specific to the _Assembler_ e.g. cache hits/misses, cache size, aggregation time, etc.