fix: Fix exception formatting by calling array_keys() #6847
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
|
could you target 3.4 please? |
|
Yes, can I change the compare branch in this same pr or do I need to open a new one? |
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.
This pull request includes a small change in the
storeObjectToPublishfunction within thePublishMercureUpdatesListener.phpfile. The change corrects the way allowed keys are displayed in an exception message.src/Symfony/Doctrine/EventListener/PublishMercureUpdatesListener.php: Modified theInvalidArgumentExceptionmessage in thestoreObjectToPublishfunction to correctly display the allowed keys by usingarray_keys(self::ALLOWED_KEYS)instead ofself::ALLOWED_KEYS.