-
-
Notifications
You must be signed in to change notification settings - Fork 218
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
feat: add priority_policy_explicit support #250
Conversation
Signed-off-by: Zxilly <zhouxinyu1001@gmail.com>
#248 Signed-off-by: Zxilly <zhouxinyu1001@gmail.com>
Signed-off-by: Zxilly <zhouxinyu1001@gmail.com>
@paul4156 please review. |
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.
I left some minor comments. Otherwise, the change looks good to me.
I am not sure if the broken test after swapping policies in example csv file is relevant or not.
Thank you very much!
@paul4156 I try to swap policies but failed to reproduce. Could you please provide more information? |
Signed-off-by: Zxilly <zhouxinyu1001@gmail.com>
Signed-off-by: Zxilly <zhouxinyu1001@gmail.com>
I cannot reliably reproduce the failure either... Please ignore. |
@Zxilly you also should add this feature to remove, update action, and add unit test for this changes. |
Signed-off-by: Zxilly <zhouxinyu1001@gmail.com>
@nodece remove a policy will not break the priority.
But it seems not atomic |
Signed-off-by: Zxilly <zhouxinyu1001@gmail.com>
Signed-off-by: Zxilly <zhouxinyu1001@gmail.com>
Signed-off-by: Zxilly <zhouxinyu1001@gmail.com>
throw error when new rule and old rule didn't have same priority Signed-off-by: Zxilly <zhouxinyu1001@gmail.com>
# [5.6.0](v5.5.0...v5.6.0) (2021-03-23) ### Features * add priority_policy_explicit support ([#250](#250)) ([763c18e](763c18e))
🎉 This PR is included in version 5.6.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Fix: #248