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

[11.x] Introduce MixManifestNotFoundException for handling missing Mix manifests #51502

Merged
merged 1 commit into from
May 20, 2024
Merged

[11.x] Introduce MixManifestNotFoundException for handling missing Mix manifests #51502

merged 1 commit into from
May 20, 2024

Conversation

xurshudyan
Copy link
Contributor

This PR introduces a new MixManifestNotFoundException to specifically handle missing Mix manifest files. This custom exception extends the base \Exception class and provides a more precise error handling mechanism for scenarios where the Mix manifest 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.

@taylorotwell taylorotwell merged commit 93658ff into laravel:11.x May 20, 2024
30 checks passed
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.

2 participants