-
Notifications
You must be signed in to change notification settings - Fork 672
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
MG-2069 - Remove relation requirement from entity unassignment #2130
Conversation
7d11d58
to
0bc0ebf
Compare
3ad6f7b
to
bdfebc7
Compare
d3042c7
to
1b94b17
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.
LGTM
672668d
to
f374c4d
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.
This starts to be a little cryptic and complex. We must simplify, but let's not do that in this PR.
bcd6de1
to
09bd9ba
Compare
Signed-off-by: WashingtonKK <[email protected]> Remove relation requirement from validate Signed-off-by: WashingtonKK <[email protected]> fix remove policies Signed-off-by: WashingtonKK <[email protected]> feat: remove policy check Signed-off-by: WashingtonKK <[email protected]> fix: ci Signed-off-by: WashingtonKK <[email protected]> fix: tests Signed-off-by: WashingtonKK <[email protected]> fix tests Signed-off-by: WashingtonKK <[email protected]> fix api docs Signed-off-by: WashingtonKK <[email protected]> fix: property based tests Signed-off-by: WashingtonKK <[email protected]> revert add policies Signed-off-by: WashingtonKK <[email protected]> Refactor relation check Signed-off-by: WashingtonKK <[email protected]> fix: ci Signed-off-by: WashingtonKK <[email protected]>
Signed-off-by: WashingtonKK <[email protected]>
Signed-off-by: WashingtonKK <[email protected]> enhance relation query Signed-off-by: WashingtonKK <[email protected]> refactor query Signed-off-by: WashingtonKK <[email protected]>
Signed-off-by: WashingtonKK <[email protected]>
Signed-off-by: WashingtonKK <[email protected]>
Signed-off-by: WashingtonKK <[email protected]>
Signed-off-by: WashingtonKK <[email protected]>
AND object_id = :object_id | ||
` | ||
if pc.Relation != "" { | ||
q = fmt.Sprintf("%s AND relation = :relation", q) |
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.
@WashingtonKK There will be only one relation in the Domain.
So no need to consider relation
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.
@WashingtonKK Please check this one and send a follow-up PR for it.
…ch#2130) Signed-off-by: WashingtonKK <[email protected]>
…ch#2130) Signed-off-by: WashingtonKK <[email protected]> Signed-off-by: JeffMboya <[email protected]>
What type of PR is this?
This is a refactor because it changes the following functionality: Unassign entity.
What does this do?
Removes the relation requirement from unassigning an entity. When the relation is provided, only the user with that relation is removed, when not provided - all relations are removed.
Which issue(s) does this PR fix/relate to?
Have you included tests for your changes?
Yes, I have included tests for my changes.
Did you document any new/modified feature?
No
Notes
Signed-off-by: WashingtonKK [email protected]