Skip to content
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

Rename and refactor SignableMsg::signable_bytes #780

Merged
merged 1 commit into from
Oct 13, 2023

Conversation

tony-iqlusion
Copy link
Member

The previous method name was sign_bytes, which as was noted in #273 is unclear to whether the resulting bytes have an appended signature.

The new name indicates that the message can be signed, but has not yet been signed.

Additionally, this commit does a bit of refactoring to eliminate some duplicated code within the method.

Closes #273

@tony-iqlusion tony-iqlusion requested a review from a team October 13, 2023 15:26
The previous method name was `sign_bytes`, which as was noted in #273 is
unclear to whether the resulting bytes have an appended signature.

The new name indicates that the message can be signed, but has not yet
been signed.

Additionally, this commit does a bit of refactoring to eliminate some
duplicated code within the method.

Closes #273
@tony-iqlusion tony-iqlusion force-pushed the rename-and-refactor-signable-bytes branch from c640ad4 to 2cd1966 Compare October 13, 2023 17:20
@tony-iqlusion tony-iqlusion merged commit d3a404f into main Oct 13, 2023
8 checks passed
@tony-iqlusion tony-iqlusion deleted the rename-and-refactor-signable-bytes branch October 13, 2023 17:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

informational: Non-signed bytes returned in sign_bytes function
2 participants