Skip to content
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow psr/log 3 #1190

Closed
wants to merge 1 commit into from
Closed

Allow psr/log 3 #1190

wants to merge 1 commit into from

Conversation

franmomu
Copy link
Contributor

@franmomu franmomu commented Dec 31, 2021

There is #1184 and #1187, but it needs a little bit more of work since there are implementations of psr/log.

@elasticmachine
Copy link
Collaborator

Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually?

@@ -32,7 +32,7 @@ class EmptyLogger extends AbstractLogger implements LoggerInterface
/**
* {@inheritDoc}
*/
public function log($level, $message, array $context = [])
public function log($level, $message, array $context = []): void
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

note that this is BC break, but given the name of the class, I guess it is not meant to be extended.

@ruudk
Copy link

ruudk commented Jan 10, 2022

@cronlabspl Can you please remove or hide your comment as it's confusing (see thread).

@ezimuel @karyna-tsymbal-atwix @jrodewig Can this PR be merged? Multiple people are now proposing the same change. This change is needed to be able to upgrade to Symfony 6.

@technige technige mentioned this pull request Jan 20, 2022
@technige
Copy link

technige commented Jan 20, 2022

This is a duplicate of #1184 and #1187, the latter of which is now closed as an exact duplicate of the former.

@franmomu We very much appreciate the extra detail you have added to this issue, but please could you instead collaborate on #1184 (the original issue), rather than opening a new one. This will help to expedite our work in reviewing and merging. Once you have done so, this issue can be closed.

@franmomu
Copy link
Contributor Author

@technige no problem merging that one!

I created this one because I was able to run the workflow jobs and the other PRs I thought they were created editing the file from Github directly, so the purpose was in fact to ease the review (avoid approving the workflow, see if the tests passes, make changes, approve again, etc), but as I said no worries at all merging the other one.

@ruudk
Copy link

ruudk commented Jan 21, 2022

This can be closed as it has been merged into #1184

@franmomu franmomu closed this Jan 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants