-
Notifications
You must be signed in to change notification settings - Fork 69
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
[ARP POA Submission] (#5) Update POA Form Submission Scopes (#101919) #21155
[ARP POA Submission] (#5) Update POA Form Submission Scopes (#101919) #21155
Conversation
Generated by 🚫 Danger |
Can you resolve the linting errors please? |
This is so that these internal methods match status params in the index endpoint. - unprocessed -> pending - resolved -> processed They have also been modified to count requests with a PoA form submission in an unsuccessful state as pending.
533709f
to
464b3aa
Compare
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.
Can you either address why the comment blocks are necessary or remove them please?
# `processed` and `not_processed` are the logical negation of one another, | ||
# but this isn't enforced structurally in the code. An application of De | ||
# Morgan's law is evident here. `invert_where` is a possibility to pull | ||
# this off too, but it's not so usable because it inverts conditions that | ||
# were chained prior. | ||
# |
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.
Can you remove the comment blocks in the file? That is not something we generally commit into the repo and the parts like An application of De Morgan's law is evident here.
are unclear.
## | ||
# This `concerning` block puts up some flashing lights around this | ||
# complexity. It potentially wants to coexist directly with other model | ||
# functionality or at a higher business logic layer, but extra care might be | ||
# needed to pull that off without making a mess. This block is especially | ||
# narrow--it only defines two scopes and no instance methods for example. | ||
# |
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.
Is this necessary?
## | ||
# The 3x `LEFT OUTER JOIN`s with very particular join conditions make | ||
# expressing both of the `processed` and `not_processed` relations easy | ||
# to express with very simple `WHERE` conditions. | ||
# |
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.
Same question
## | ||
# Must be resolved, and either the resolution is not an acceptance, or if | ||
# it is, there must be a form submission that succeeded. | ||
# |
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.
Here too
## | ||
# Must be unresolved, or the resolution is an acceptance and there also | ||
# must not be a form submission that succeeded. | ||
# |
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.
And here
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.
Thanks for addressing those!
f641d0a
to
2d34edc
Compare
No description provided.