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
feat: allow disabling storage persistence #1539
feat: allow disabling storage persistence #1539
Conversation
Looking good, just the test is broken. Feel free to merge if the CI is green (maybe also try running e2e tests to be sure, but we dont need to wait for the platform ones to finish). |
Test was broken because I forgot to update it when I renamed the option 😬 |
Now it seems to be timeouting |
|
||
expect(directoryFiles).toHaveLength(0); | ||
// We check that reading the directory for the store throws an error, which means it wasn't created on disk | ||
await expect(() => readdir(expectedPath)).rejects.toThrow(); |
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.
FYI the argument does not have to be callback (as long as its async), this should work the same:
await expect(() => readdir(expectedPath)).rejects.toThrow(); | |
await expect(readdir(expectedPath)).rejects.toThrow(); |
At least that is how I use it, if there is a reason to prefer the callback approach, let me know :]
Resolves the request in #1533