Blade template not resolved

[shaffe-fr]

Hello,

When an exception is thrown inside a view, the compiled cache view is shown instead of the initial blade template.

Is this the intended behaviour?

Thanks, Karel

[jcmcclorey]

I have the same question, the previous setup in Laravel used the regular blade view and I would like to get that functionality back. It's a real pain to try to match up the compiled view with the blade view

[VincentVanWijk]

Same problem here, also want to point out the edit links also link to the compiled view, so when I click the 'pencil', the wrong file opens in phpstorm.

edit: The 'Collapse vendor frames' also doesn't work

on Windows, using :

php: 8.1 laravel/framework: 9.37 spatie/larvel-ignition: 1.61

[SocolaDaiCa]

@shaffe-fr @VincentVanWijk Fixed https://github.com/spatie/laravel-ignition/releases/tag/1.6.4

[ghost]

@SocolaDaiCa Perhaps out of scope for this issue, but the collapse vendor frames button does not work yet. I was hoping it had something to do with the paths that were fixed with your pull request

[SocolaDaiCa]

@Vincent-avant what is collapse vendor. Could you explain It.

[ghost]

@SocolaDaiCa As you can see on the screenshot at the top of this issue, there is a button on the top-left named "collapse vendor frames".

It collapses the stack trace on the left, to filter out the method calls of the framework itself, and only shows you 'your' files, if I understand it correctly.

You can see it working in this video on Freek van der Herten's channel : https://www.youtube.com/watch?v=LEY0N0Bteew&t=739s

You can see a dropdown in the video that says "7 vendor frames" and "44 vendor frames". This is what is currently not working on windows, the button does not collapse the stack trace.

[shaffe-fr]

I have the same issue on Windows. You can maybe create a dedicated issue @Vincent-avant ?