-
Notifications
You must be signed in to change notification settings - Fork 446
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: Remove unnecessary async methods in crypto
package
#1949
Labels
good first issue
Good issue for new contributors
help wanted
Seeking public contribution on this issue
P1
High: Likely tackled by core team if no one steps up
Comments
maschad
added
help wanted
Seeking public contribution on this issue
good first issue
Good issue for new contributors
labels
Aug 9, 2023
Seems like any async functions with |
That's a good place to start but not all async functions with that comment are necessarily sync such as the aes-gcm encrypt function which incorrectly has this comment. Would you mind opening a PR to address this? |
This was referenced Aug 11, 2023
achingbrain
pushed a commit
that referenced
this issue
Aug 14, 2023
achingbrain
added a commit
that referenced
this issue
Nov 27, 2023
Removed async keyword from function which don't: 1) do any async work 2) return a promise 3) have an async browser equivalent Closes: #1949 --------- Co-authored-by: Chad Nehemiah <chad.nehemiah94@gmail.com> Co-authored-by: achingbrain <alex@achingbrain.net>
maschad
added a commit
to maschad/js-libp2p
that referenced
this issue
Nov 27, 2023
Removed async keyword from function which don't: 1) do any async work 2) return a promise 3) have an async browser equivalent Closes: libp2p#1949 --------- Co-authored-by: Chad Nehemiah <chad.nehemiah94@gmail.com> Co-authored-by: achingbrain <alex@achingbrain.net>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
good first issue
Good issue for new contributors
help wanted
Seeking public contribution on this issue
P1
High: Likely tackled by core team if no one steps up
I think we now have a load of async functions that don't do any async work - we should remove the async keyword from them to prevent promises being created unnecessarily but that can be done in a follow-up.
Originally posted by @achingbrain in #1939 (review)
The text was updated successfully, but these errors were encountered: