-
Notifications
You must be signed in to change notification settings - Fork 429
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
Revert disk cache store #1062
Revert disk cache store #1062
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.
Looks good @afcapel.
It's a shame if the disk cache doesn't end up making it into v8, but I agree with you about the priorities so it's a good call to take it back out for now.
@@ -62,11 +62,11 @@ setup(() => { | |||
Turbo.registerAdapter(adapter) | |||
}) | |||
|
|||
test("navigator adapter is native adapter", async () => { | |||
test("test navigator adapter is native adapter", async () => { |
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.
I think the extraneous test
in the descriptions were removed after the original changes were added, and so reverting is bringing some of them back. Might we worth removing them again as an additional commit in this PR, for consistency?
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.
Good point, I've added the commits to the branch.
The branch was gone, so I had to recreate the commits. Definitely one case in which squashing the branch was not very helpful.
* origin/main: Revert disk cache store (#1062)
This reverts #949 and the follow up PRs #1014 and #1056.
The idea is still appealing but we've found several hard-to-debug issues while testing this in our applications. Most notably we found some meta tags propagating outside the original page on navigation, and issues with the timing of
turbo:load
events.These issues are solvable, but our priority right now is shipping Page Refreshes ahead of Turbo v8.