Let document subscription stream updates from materializer #605
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Best reviewed commit by commit
The subscription field for receiving updates about a specific document is updated to trigger sending a new update whenever the materializer finishes a new version of it.
This required changing up the message bus and service manager a bit to allow receiving updates about newly updated documents from within the
http
service.Context
receives a new field containing the service sender, which is now constructed outside the service manager and passed in to it as a parameter.Then, a new message type
DocumentUpdated
is added, which is emitted in the reducer task whenever documents are created or updated. This lets use then connect any running subscription stream to the service bus and listen for updates of their queried document.📋 Checklist
CHANGELOG.md