We need support for more artifacts.
In order for Reducers to properly work, we need read models and JSON Schema support to populate the server with. We should use the most popular library for representing JSON Schema and we can use reflect-metadata and reflection for this. So preferably we'd find a library that supports this using reflection automatically where we can hand it a type and it will come back with a JSON Schema. We also need this for registering EventTypes.
Then, we need to have support for Constraints and Projections. For Projections we have both the ModelBound and the Declarative. We need both. But projection builders should use the decorator pattern for discoverability.
All artifacts hooked up into the ClientArtifactsProvider.
See how things are done in the C# client:
https://github.com/Cratis/Chronicle/tree/main/Source/Clients/DotNET
We need support for more artifacts.
In order for Reducers to properly work, we need read models and JSON Schema support to populate the server with. We should use the most popular library for representing JSON Schema and we can use
reflect-metadataand reflection for this. So preferably we'd find a library that supports this using reflection automatically where we can hand it a type and it will come back with a JSON Schema. We also need this for registering EventTypes.Then, we need to have support for Constraints and Projections. For Projections we have both the ModelBound and the Declarative. We need both. But projection builders should use the decorator pattern for discoverability.
All artifacts hooked up into the ClientArtifactsProvider.
See how things are done in the C# client:
https://github.com/Cratis/Chronicle/tree/main/Source/Clients/DotNET