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

Explain how to test Deno KV code locally #313

Merged
merged 2 commits into from
Apr 14, 2024
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Update deploy/kv/manual/index.mdx
  • Loading branch information
thisisjofrank authored Apr 14, 2024
commit 5564dae6cd9dd19721768d98c710fa1f0e009eaa
2 changes: 1 addition & 1 deletion deploy/kv/manual/index.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -239,7 +239,7 @@ by your code. Learn more about Deno KV on Deno Deploy [here](./on_deploy.mdx).

## Testing

By default, [`Deno.openKv()`](https://www.sqlite.org/inmemorydb.html) creates or
By default, [`Deno.openKv()`](https://deno.land/api?unstable=&s=Deno.openKv) creates or
opens a persistent store based on the path from which the script that invoked it
was run. This isn't usually desireable for tests, which need to produce the same
behavior when run many times in a row.
Expand Down
Loading