fix(logging): write only specific fields for user logging #264
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
This was referenced Jun 13, 2020
WikiRik
approved these changes
Jun 13, 2020
serge1peshcoff
pushed a commit
that referenced
this pull request
Jun 13, 2020
## [1.0.1](1.0.0...1.0.1) (2020-06-13) ### Bug Fixes * **logging:** write only specific fields for user logging ([#264](#264)) ([7c024cd](7c024cd))
|
🎉 This PR is included in version 1.0.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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.
for now, we are writing the whole user object (with bodies, circles, join requests etc.) when logging requests, that's too much. this is the copypaste of the core thing I have (which has it right from the start), which logs only specific fields, also I'll add it to other services later.