-
Notifications
You must be signed in to change notification settings - Fork 60
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
fix(authorization): revert already set error #652
Conversation
Rubilmax
commented
Dec 18, 2023
- Fixes various fixes #630 (comment)
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.
Should also remove the corresponding test, but otherwise LGTM
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.
we don't delete it for setAuthorization
? I feel this is useless as well and a bit weird to have 2 different requirements for the same functionality
This argument can also be used to defend the introduction of such requirement: why would we require not already set fee but not in setAuthorization* functions? In the end, I am convinced we were inconsistent, though I am not convinced it is a big deal... |
But now we're being weirdly inconsistent it's even more disturbing to me |
Mb I wasn't clear: I was arguing we shouldn't revert the change at all! |
Another rationale behind this PR would be to simply revert the changes to the old way, even if it can be considered inconsistent, because it still works and there's no big deal |
For You can also look at it another way: we are never in the "already set" case for |
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
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.
Let's add a comment no?
Something like: |
LGTM |