-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
refactor: deno_crypto op crate #7956
refactor: deno_crypto op crate #7956
Conversation
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.
@littledivy Thanks for this patch - I think this looks good and is on the right track.
I'm wondering why you're working on this? Do you need this yourself - or just thought it'd be a good clean up?
Would you mind patches for moving most of the ops? – I didn't attempt to refract all of them in this PR as I wanted to know the core team's opinion. |
Thanks @littledivy but we should hold off on moving more crates - it's not exactly clear yet how we should handle reexports and where to draw crates boundaries; additionally remaining JS runtime code is quite dependent on some code that is specific to |
Should be ready to land 👍 |
merged master. |
@littledivy please rebase, I'm still interested in landing this PR |
@bartlomieju Updated. 👍 (sorry for the delay) |
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.
LGTM
Thank you @littledivy, hopefully this refactor will kick-off webcrypto
APIs
This commit factors out "deno_crypto" op crate. "rand" crate dependency was consequently moved to "deno_crypto" crate and reexported.
Moves crypto to its own op_crate