migrate from turbolinks to turbo drive #1834
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
|
Yuck. Thanks for doing the footwork, @chappjc. I'll get into it. |
Member
Author
|
Turns out a CSP with |
Member
Author
|
Just saw that Turbo 7 was released a few days ago. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This starts the migration from Turbolinks to Turbo Drive. Help needed.
We are using some wacky Turbolinks hacks to deal with url query and patge anchor navigation issues.
turbolinks/turbolinks#75 (comment)
The above is apparently no longer needed with Turbo Drive, but I don't follow how TurboQuery works or how to remove it. See hotwired/turbo#125
#845
#870
#814
#815
I'm pretty sure we need to nuke TurboQuery now, but someone else will need to pick this up.