[Messenger] Don't mark EnvelopeAwareExceptionInterface internal
#54859
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
valtzu
force-pushed
the
expose-envelope-aware-interface
branch
from
846a35f
to
7713fd1
Compare
|
Do we also want to remove the |
Either way, I don't mind – but f.e. |
fabpot
approved these changes
May 7, 2024
|
Thank you @valtzu. |
Merged
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.
As discussed here, let's expose
EnvelopeAwareExceptionInterfaceto allow custom Messenger middlewares throw a custom exception without causing stamps from previous middlewares being dropped.