Suggested Documentation change
The event chapter of the reference guide has seen the highest amount of attention during #3961.
We're confident that the flow of the pages and sections there is beneficial for the query chapter too.
Hence, it would be good to validate if both align sufficiently so.
If the query chapter deviates, we should adjust it such that it aligns.
Pointers to take note of when validating and ensuring the alignment are:
- The
index.adoc contains a short intro paragraph, a list of topic-specific terms with one liner description, and and overview of that chapter. And nothing more.
- The
handlers.adoc provides an introduction explaining handlers and handling components, a section on how to register handlers, a section on how handlers are resolved to send a message to, and an explanation about handler return types.
- The
dispatchers.adoc provides an introduction explaining the logic spots to dispatch from, the available infrastructure to dispatch with and explanation + examples when and how to use these.
- The
infrastructure.adoc provides a short intro listing all infracomponents, and each of these components is given an explanation when they're valuable.
Suggested Documentation change
The event chapter of the reference guide has seen the highest amount of attention during #3961.
We're confident that the flow of the pages and sections there is beneficial for the query chapter too.
Hence, it would be good to validate if both align sufficiently so.
If the query chapter deviates, we should adjust it such that it aligns.
Pointers to take note of when validating and ensuring the alignment are:
index.adoccontains a short intro paragraph, a list of topic-specific terms with one liner description, and and overview of that chapter. And nothing more.handlers.adocprovides an introduction explaining handlers and handling components, a section on how to register handlers, a section on how handlers are resolved to send a message to, and an explanation about handler return types.dispatchers.adocprovides an introduction explaining the logic spots to dispatch from, the available infrastructure to dispatch with and explanation + examples when and how to use these.infrastructure.adocprovides a short intro listing all infracomponents, and each of these components is given an explanation when they're valuable.