Advice: prepare error fallback customizing

[nael94]

I'd like to customize error fallbacks pages to integrate your framework with mine. I noticed that I can't handle and customize errors that each time occurs.

[carloscarucce]

Hi @nael94 how would you suggest?

[nael94]

Hi @carloscarucce I think about a way to customize a customized outputted error messages especially in case of recursive partials and layouts and passing variables. I've had a serious tragedy with that issue (exactly in parsing processes like commenting and passing variables in a custom tags, aaaaah so bad!) and I've solved it but I still don't feel comfort with my solution (but it does the job as possible, until now I think).

We may have a direct contact to negotiate about that later because I've done that for months from now.

[nael94]

Okay the errors are not clear as expected for ease of debugging. I've suffered diving in the Crow classes for trying to detect the responsible line. I know that the errors might be occurred by the developer (as usual) but in case of no error referring: this would be like seeking for a needle in haystack.

One of them is in this case:

<x-my-component :datalist="[1, 2, 3, 4]" /> // this leads to failure

To solve this trick, I had to do something like this:

@php
  $list = [1, 2, 3, 4];
@endphp
<x-my-component :datalist="$list" /> // this works as well

Pay attention that if I want to use this variable in multiple sections in that one view file: I have to declare it with a new name (or try to pass it in the Controller in MVC case) so for that I've suggested to declare this php scope once in that view file at the top and then use it how many times you want in that file; this would be cleaner and better, I think so.

[nael94]

In general, mentioning errors and output them clearly to the developer to fix it (for now) is not clear to catch. If there is a better way to inform, or a customizable components to use would be much better.

However, I've created a pull request with my fixes. It's my pleasure to have a look to see my fixes and new features there.

[nael94]

For importance, refer to this comment in my pull request #18 (comment)