com.avsystem.commons.annotation
AnnotationAggregate
Related Doc:
package annotation
Dummy type member meant to be redefined in order to have aggregated annotations applied on it.
Dummy type member meant to be redefined in order to have aggregated annotations applied on it. These annotations will be automatically picked up by macro engines each time they encounter the aggregating annotation itself. Other than being an "anchor" for annotations, this type member has no actual meaning and there is no reason to ever actually use it. NOTE: a less weird solution would be to put aggregated annotations on the aggregating annotation class itself, but this would make it impossible to access the arguments of aggregating annotation in aggregated annotations.
Base trait for annotations which aggregate multiple other annotations. This way annotation aggregates work like "annotation functions" - they are annotations that yield more annotations.
In order to specify aggregated annotations, the class that extends
AnnotationAggregatemust redefine theImplieddummy type member and apply the aggregated annotations on it. Macro engines used inGenCodecmaterialization and RPC framework will automatically pick up these annotations.In the above example, applying
@mongoIdannotation on theidfield has the same effect as if annotations@name("_id") @outOfOrderwere applied directly on that field.NOTE: thanks to the fact that aggregated annotations are applied on a type member you can pass the arguments of original annotation to aggregated annotations, e.g.