You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What is the difference between using the @trail directive VS the php artisan trail:generate command?
Performance? Security? ...?
Using the directive seems like the easiest option, but the fact that you didn't write it as first default solution makes me think it has some hidden downsides?
You mentioned that using the directive makes all application routes available in the window object, making them visible to end users. However, when generating the routes.json, aren't these routes also included in the final output bundle (.js) file?
I'm considering both options, so any info would be appreciated :)
Thanks
The text was updated successfully, but these errors were encountered:
Great package, thanks!
What is the difference between using the
@trail
directive VS thephp artisan trail:generate
command?Performance? Security? ...?
Using the directive seems like the easiest option, but the fact that you didn't write it as first default solution makes me think it has some hidden downsides?
You mentioned that using the directive makes all application routes available in the window object, making them visible to end users. However, when generating the routes.json, aren't these routes also included in the final output bundle (.js) file?
I'm considering both options, so any info would be appreciated :)
Thanks
The text was updated successfully, but these errors were encountered: