Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork9.7k
Revert "feature #27801 [MonologBridge] Add ProcessorInterface, enabling autoconfiguration of monolog processors"#28845
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Merged
Uh oh!
There was an error while loading.Please reload this page.
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
ogizanagi approved these changesOct 13, 2018
fabpot approved these changesOct 13, 2018
Member
fabpot commentedOct 13, 2018
Thank you@nicolas-grekas. |
fabpot added a commit that referenced this pull requestOct 13, 2018
…rface, enabling autoconfiguration of monolog processors" (nicolas-grekas)This PR was merged into the 4.2-dev branch.Discussion----------Revert "feature#27801 [MonologBridge] Add ProcessorInterface, enabling autoconfiguration of monolog processors"This reverts commitf27c3a8, reversingchanges made to9da0454.| Q | A| ------------- | ---| Branch? | 4.2| Bug fix? | no| New feature? | no| BC breaks? | no| Deprecations? | no| Tests pass? | yes| Fixed tickets | -| License | MIT| Doc PR | -A bridge shouldn't provide interfaces to me so I submittedSeldaek/monolog#1204 instead.This PR reverts the possibility to autoconfigure processors for now, so that it could be moved to the MonologBundle instead.To have TokenProcessor and WebProcessor classes implement the new ProcessorInterface, we could bump the minimum version of monolog. This cannot be done until a new version of it is tagged, so we need to resolve this before tagging 4.2 ourselves.Commits-------cfc3f25 Revert "feature#27801 [MonologBridge] Add ProcessorInterface, enabling autoconfiguration of monolog processors (nicolas-grekas)"
javiereguiluz added a commit to symfony/symfony-docs that referenced this pull requestNov 9, 2018
This PR was merged into the master branch.Discussion----------[Monolog] Move ProcessorInterface to MonologSincesymfony/symfony#27801 was reverted insymfony/symfony#28845 and the new plan being to make this interface part of Monolog.Commits-------663f2ea [Monolog] Move ProcessorInterface to Monolog
Sign up for freeto 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.
This reverts commitf27c3a8, reversing
changes made to9da0454.
A bridge shouldn't provide interfaces to me so I submittedSeldaek/monolog#1204 instead.
This PR reverts the possibility to autoconfigure processors for now, so that it could be moved to the MonologBundle instead.
To have TokenProcessor and WebProcessor classes implement the new ProcessorInterface, we could bump the minimum version of monolog. This cannot be done until a new version of it is tagged, so we need to resolve this before tagging 4.2 ourselves.