LOG_DEPRECATIONS_CHANNEL is set to stack in .env.example #6397
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
|
Feel free to do this in your own app 👍 |
I've successfully implemented it, and now I can track warnings in my laravel.log file right from the inception of development. |
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.
Setting
LOG_DEPRECATIONS_CHANNEL=stackinstead ofLOG_DEPRECATIONS_CHANNEL=nullis beneficial because it ensures that deprecation warnings and errors from PHP or packages are logged, helping to catch potential issues early on and avoid overlooking them during the initial stages of development with Laravel.