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

refactor: make challenge/origin arguments less confusing #158

Merged
merged 1 commit into from
Apr 9, 2019

Conversation

grzuy
Copy link
Contributor

@grzuy grzuy commented Apr 9, 2019

Motivated by conversation in #150.

"original" is confusing here. It was intended to mean the original value when the ceremony started, but it might confuse by lead to think that during the Authentication ceremony, this is asking for the original value from the Registration, which is not what we want.

I considered naming them just challenge and origin , but I ended up with expected_challenge and expected_origin, because I was afraid that reading response.verify(challenge, origin) could lead to the potential confusion that this arguments are the ones being verified for correctness, when they are actually the expected values, and the things being verified are the ones "inside" the response.

However, not strong on that if someone else prefers shorter names.

Copy link
Member

@brauliomartinezlm brauliomartinezlm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sounds good to me 👍

@grzuy grzuy merged commit 8383a73 into master Apr 9, 2019
@grzuy grzuy deleted the clarify_arguments branch April 9, 2019 20:58
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.

None yet

2 participants