Increasing LiveComponentSubscriber ExceptionEvent priority to avoid excess logging #660
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.
Hi!
If you use the
ComponentWithFormTrait
, when validation fails, aUnprocessableEntityHttpException
is thrown. This is caught by theExceptionEvent
listener onLiveComponentSubscriber
, which renders the component. It's a very normal, excepted flow.However, currently, the
LiveComponentSubscriber
may run after the coreErrorListener
as both have a priority of 0. By making our subscriber run first, it avoids unnecessary logging of UnprocessableEntityHttpException by that listener.Caught in the wild on the Symfonycasts code 🎥
Cheers!