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.
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
Use LZ4 with WASM for volume saving/undo/redo #6652
Use LZ4 with WASM for volume saving/undo/redo #6652
Changes from 14 commits
d029734
b0e4ed8
ec39a18
d8c79b0
c4bb49b
1724ea2
7e60e85
ddf9f5c
6384566
b6d7f24
194c0b8
2b9cc24
f96cb64
3a0abd8
df53044
062f846
c86c647
738d29f
7f19d04
dad8f0d
f581e79
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Instead of importing the mock in every test file, I think it should work and would be more foolproof to import it once in
frontend/javascripts/test/enzyme/e2e-setup.ts
or do you think the import order could be problematic, then? 🤔Sorry to comment on the mocking again. It's no big deal if you leave it as-is.
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.
the
stopAll
s reverted the lz4 mocking (which is necessary since the lz4-wasm module is different for browser and node, unfortunately). it took me a while to figure out that stopAll was the culprit, since it's so inconspicuously in the code. luckily, these statements weren't even necessary.it's a bit unfortunate that the lz4 mock needs to be at that many places, but I couldn't figure out a better way..