-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Debug turbo events in development #16706
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice!
'turbo:click', | ||
'turbo:before-visit', | ||
'turbo:visit', | ||
'turbo:submit-start', | ||
'turbo:before-fetch-request', | ||
'turbo:before-fetch-response', | ||
'turbo:submit-end', | ||
'turbo:before-cache', | ||
'turbo:before-render', | ||
'turbo:before-stream-render', | ||
'turbo:render', | ||
'turbo:load', | ||
'turbo:frame-render', | ||
'turbo:frame-load', | ||
'turbo:fetch-request-error', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Better to sort alphabetically
Also why not all events, maybe turbo:before-morph-element
, turbo:before-morph-attribute
andturbo:morph-element
will spam, and turbo:frame-missing
will be visible anyway, but why not turbo:morph
, turbo:before-frame-morph
, turbo:before-frame-render
, turbo:before-prefetch
, turbo:reload
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
will add them 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In development mode, output all turbo events to console so we can observe what happens during navigation