Allow inspecting the originating JSON for a message #303
Conversation
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
Introduce non-serializable keys in the additional properties dictionary for messages (those that start with `__`) so that apps can leverage them for internal-only, transient data that doesn't need serialization at all. Then right after deserializing a message, place the originating JSON as-is in that dictionary as `__json` and expose as internal property for debugging purposes. Note we explicitly don't make this part of the public API (for now?).
Member
Author
|
🧪 Details on Ubuntu 24.04.3 LTSfrom dotnet-retest v0.7.2 on .NET 9.0.9 with 💜 by @devlooped |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Allow inspecting the originating JSON for a message
Introduce non-serializable keys in the additional properties dictionary for messages (those that start with
__) so that apps can leverage them for internal-only, transient data that doesn't need serialization at all.Then right after deserializing a message, place the originating JSON as-is in that dictionary as
__jsonand expose as internal property for debugging purposes. Note we explicitly don't make this part of the public API (for now?).