Support for masking sensitive debug data #4550
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
Sometimes we want to hide sensitive information from the debug trace, even if it's only for the development environment. This makes it possible.
paulbalandan
requested changes
Apr 11, 2021
Co-authored-by: John Paul E. Balandan, CPA <[email protected]>
paulbalandan
approved these changes
Apr 12, 2021
paulbalandan
approved these changes
Apr 16, 2021
5 tasks
kenjis
added
enhancement
kenjis
reviewed
Jul 14, 2023
| * -------------------------------------------------------------------------- | ||
| * Any data that you would like to hide from the debug trace. | ||
| * In order to specify 2 levels, use "/" to separate. | ||
| * ex. ['server', 'setup/password', 'secret_token'] |
There was a problem hiding this comment.
What is 'server' in the example? What is level ?
What does this feature hide?
Does this feature really work?
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.
Description
Sometimes we want to hide sensitive information from the debug trace, even if it's only for the development environment.
This makes it possible.
To give more context to this matter, here's a link that addresses a similar issue on laravel: laravel/ideas#1236
Checklist: