[2.x] Support for checking if the component exists when rendering #749
Conversation
This file contains hidden or 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
|
@pascalbaljet I would get the value for config ensure_pages_exist from an env() for who wants to enable it only in development and not in production |
Good point, that also nicely aligns with the other config options. Added in 88d55d7 |
This was
linked to
issues
Jun 20, 2025
This was referenced Jun 26, 2025
adrum
added a commit
to adrum/InertiaCore
that referenced
this pull request
Sep 21, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 brings support for checking whether a component exists when sending it to the frontend using
Inertia::render(). This idea was brought up in #272. It uses the same logic as that in theAssertableInertiaclass, but you can configure it separately from each other.I think I would not enable this in production (though it's always enabled with Blade), but definitely in development. There's no clear indication on the frontend when you pass the wrong component, and I've been bitten by this a few times, so this would be a nice timesaver.