Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Question] trail:generate VS @trail directive #23

Open
sebsobseb opened this issue Jun 21, 2024 · 0 comments
Open

[Question] trail:generate VS @trail directive #23

sebsobseb opened this issue Jun 21, 2024 · 0 comments

Comments

@sebsobseb
Copy link

sebsobseb commented Jun 21, 2024

Great package, thanks!

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant