[11.x] Introduce MixManifestNotFoundException for handling missing Mix manifests
#51502
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
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 PR introduces a new
MixManifestNotFoundExceptionto specifically handle missingMixmanifest files. This custom exception extends the base\Exceptionclass and provides a more precise error handling mechanism for scenarios where theMixmanifest cannot be found.By using a specific exception, we can distinguish Mix manifest errors from other exceptions, allowing for more precise error handling. This enables developers to implement custom exception handling logic more reliably. For example, developers can choose not to display custom error pages if the Mix manifest is missing. This is important because, without the Mix assets, the custom error pages might not render correctly.