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

fix: persist dev experimental storage state in feature specific dirs #839

Merged
merged 1 commit into from
Apr 25, 2022

Conversation

threepointone
Copy link
Contributor

With --experimental-enable-local-persistence in dev, we were clobbering a single folder with data from kv/do/cache. This patch gives individual folders for them. It also enables persistence even when this is not true, but that stays only for the length of a session, and cleans itself up when the dev session ends.

Fixes #830

@changeset-bot
Copy link

changeset-bot bot commented Apr 24, 2022

🦋 Changeset detected

Latest commit: c12473d

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
wrangler Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@github-actions
Copy link
Contributor

github-actions bot commented Apr 24, 2022

A wrangler prerelease is available for testing. You can install this latest build in your project with:

npm install --save-dev https://prerelease-registry.developers.workers.dev/runs/2218529512/npm-package-wrangler-839

You can reference the automatically updated head of this PR with:

npm install --save-dev https://prerelease-registry.developers.workers.dev/prs/839/npm-package-wrangler-839

Or you can use npx with this latest build directly:

npx https://prerelease-registry.developers.workers.dev/runs/2218529512/npm-package-wrangler-839 dev path/to/script.js

Copy link
Contributor

@petebacondarwin petebacondarwin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

NIT, I would now change the variable name from localPersistencePathOrDisableLocalPersistence to localPersistencePath setting it to null if the user does not want to enable local persistence. This is because we are strictly not disabling persistence any more.

@threepointone
Copy link
Contributor Author

Good recco, doing so. Thanks!

With `--experimental-enable-local-persistence` in `dev`, we were clobbering a single folder with data from kv/do/cache. This patch gives individual folders for them. It also enables persistence even when this is not true, but that stays only for the length of a session, and cleans itself up when the dev session ends.

Fixes #830
@threepointone threepointone force-pushed the fix-dev-local-persistence-paths branch from 447cdd2 to c12473d Compare April 25, 2022 07:00
@threepointone threepointone merged commit f2d6de6 into main Apr 25, 2022
@threepointone threepointone deleted the fix-dev-local-persistence-paths branch April 25, 2022 07:07
@github-actions github-actions bot mentioned this pull request Apr 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants