Say which serialization boundary a claimed read model crosses - #2534
Merged
Conversation
The page explained which provider wins and why compliance makes Chronicle the one that has to, but not the consequence that costs people time: the winner also decides how the injected instance is materialized, and the three providers cross entirely different boundaries. A consumer whose MongoDB convention, element rename or custom serializer does not apply to a command-side read model had no way to learn why from the documentation, and the failure is quiet and directional - the customization works plainly on the query side, which is the surface anybody checks first, so it looks discovered and correct while reaching nothing on the command path. The API's own remarks already say this. The page a consumer reads did not. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: 49eab3a7-0743-4895-8303-bf5632b6a992
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Changed