Support arrays in parameters value logging #24596
Merged
Conversation
This file contains 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
|
Why 5 items? |
|
Just because :) The byte[] formatting truncates at 32 bytes, also arbitrary. Arrays can contain anything - including strings - so a significantly lower number seems like a good idea to not generate too much logging. I think it should be seen as something that allows more or less identifying which parameter it was, rather than providing the full value. |
AndriySvyryd
approved these changes
Apr 7, 2021
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
Note that this will capture any IList, which may be a bit wide (Npgsql supports arrays and generic lists).
Closes #24595