Skip to content

View path errors result in impossible to debug frontend errors #727

@gvlasov

Description

@gvlasov

How to reproduce:

  1. Have any working Inertia rendering route like:
return Inertia::render('Contacts', []);
  1. Break the view name:
return Inertia::render('ContactZ', []);

What I would expect to happen: an error on frontend saying something like Missing view 'ContactZ', or maybe intertia adapter throwing error 500 with the same text.

What actually happens: no server-side errors and this frontend error:

Image

This issue makes refactoring views unnecessarily difficult.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions