fix: add condition for getrandom dependency#504
Conversation
Summary of ChangesHello @Its-Just-Nans, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request enhances the zip crate's compatibility with WebAssembly by making the getrandom dependency conditional on the target architecture and introducing a new testing suite specifically for WASM environments. These changes address a reported issue related to getrandom in WASM and establish a robust testing framework for future WASM-related developments. Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
There was a problem hiding this comment.
Code Review
This pull request aims to fix an issue with aes-crypto on wasm32 targets by adjusting the getrandom dependency features. It introduces target-specific dependencies for getrandom in Cargo.toml and adds a new wasm32 test file.
My review focuses on the correctness of the dependency configuration and the new test code. I've found a critical issue in Cargo.toml regarding the getrandom version and feature flags which will prevent the wasm build from succeeding. I've also suggested improvements in the new test file to remove unused imports and reduce code duplication. Overall, the approach is correct, but these changes are needed to make it work and improve maintainability.
|
FYI console_error_panic_hook was removed in: |
|
rustversion 1.0.0 |
|
Looks good in principle, but this build error needs fixing: Maybe we need a newer version of the |
Yes exactly but the |
getrandom dependency
|
Maybe we could wait for an answer wasm-bindgen/wasm-bindgen#4899 EDIT: The merge of wasm-bindgen/wasm-bindgen#4899 will not help today since we depends on wasm-bindgen@0.2.100 but maybe in the future when our dependencies will use ^0.2.106 |
Well, the build error has disappeared one way or another, which is good enough for me for at least |
Okay I will do a tracking issue if this MR is merged btw, should I add wasm-pack tests in CI? |
Should fix #336 no?
Should I change the CI to run the wasm-pack tests?