Allow to exclude route(s) from Turbo's prefetching mechanism

[angtheod]

Hello @tabuna and thank you for your work!
Is there a way currently to exclude (via configuration or code) one or more routes from the prefetching mechanism?

If not then it might be useful to have this type of configuration.
For example, it's useful to exclude the logout route.

=EDIT=
Nevermind, a few minutes later, I answered my own question.
I saw that you give the option to disable Turbo's prefetching on a per-element basis by setting the data-turbo attribute of the element.

e.g.

Menu::make(__('Logout'))
     ->route('admin.logout')
     ->set('turbo', false)
     ->id('logout')
     ->icon('logout'),

[tabuna]

Hi there!
Since logout is inherently a destructive action, it’s best to avoid using it via a GET request whenever possible.

[angtheod]

thanks, that is true. I was too focused on fixing the prefetch problem with logout... that I missed the more basic problem :)

[angtheod]

Hmm, I have a question.
Since, the Menu performs a GET request, does this mean I need to use a Button?
And how can I include a Button like this in the MainMenu (so that the user sees a Logout at the bottom of the main menu)?
Or is there another way to go about this?

[tabuna]

This is done intentionally - I believe it’s not quite right to place destructive actions (like POST requests) directly into a menu. Of course, you can work around this by using data attributes, for example by adding data-turbo-method="POST".

By the way, could you share what you didn’t like about the default setup where the logout button is placed in the profile menu? It’s not something that users typically need very often, so having it there usually makes sense.