Improve error messages for "no component found matching phx-target" error #3619
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.
When "no component found" errors occur, they are extremely difficult to debug ("What component did we expect to exist at target 2? 🤷♂️"). This improves the
console.error
log to include the element we expected the component to exist within, which should help at least somewhat.It might be worth throwing an exception here so that people's automated exception tracking (Sentry, etc.) will pick it up. Since the LiveView is effectively dead in the water at this point, it seems like something that it'd be good to have more observability around. I didn't include that change in this PR, but I'm happy to do so if it's desired.