-
Notifications
You must be signed in to change notification settings - Fork 41
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
[ADD] cooperator_worker_force #461
Conversation
@tfrancoi I moved all the worker_store relayed stuff in a separated module. This should not affect polln but it might be a good idea to have a look. |
a66008a
to
e85cfdb
Compare
@polchampion This is deployed on test server (except demain). The Force Worker functionality was moved to a new module
|
e85cfdb
to
f80c887
Compare
Codecov Report
@@ Coverage Diff @@
## 12.0 #461 +/- ##
===========================================
+ Coverage 39.26% 60.76% +21.50%
===========================================
Files 44 153 +109
Lines 1541 5251 +3710
Branches 293 926 +633
===========================================
+ Hits 605 3191 +2586
- Misses 933 1917 +984
- Partials 3 143 +140
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
@robinkeunen Sucessfully tested on lepedalo-test
|
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.
Just one comment, I am not finished ;)
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.
About the whole worker/allow_working logic, wouldn't it be simpler to set is_worker
as a related field from the share's allow_working
?
- The field related field could be stored, so we wouldn't have to write search methods
- The field could be not readonly, so it could be modified on the interface.
I would be a simpler design indeed but a cooperator can have multiple shares so a simple related field won't do. We could have a "main share" field like "main seller" but it would be part of bigger refactoring which is already part of issue OCA/cooperative#18 |
Ah yes, forgot about that 👍 |
This PR has the |
/ocabot merge major |
What a great day to merge this nice PR. Let's do it! |
@robinkeunen your merge command was aborted due to failed check(s), which you can inspect on this commit of 12.0-ocabot-merge-pr-461-by-robinkeunen-bump-major. After fixing the problem, you can re-issue a merge command. Please refrain from merging manually as it will most probably make the target branch red. |
/ocabot merge major |
Hey, thanks for contributing! Proceeding to merge this for you. |
@robinkeunen your merge command was aborted due to failed check(s), which you can inspect on this commit of 12.0-ocabot-merge-pr-461-by-robinkeunen-bump-major. After fixing the problem, you can re-issue a merge command. Please refrain from merging manually as it will most probably make the target branch red. |
@robinkeunen your merge command was aborted due to failed check(s), which you can inspect on this commit of 12.0-ocabot-merge-pr-461-by-robinkeunen-bump-major. After fixing the problem, you can re-issue a merge command. Please refrain from merging manually as it will most probably make the target branch red. |
/ocabot rebase |
Congratulations, PR rebased to 12.0. |
f80c887
to
38b3d14
Compare
/ocabot merge major |
What a great day to merge this nice PR. Let's do it! |
Congratulations, your PR was merged at 775bb55. Thanks a lot for contributing to beescoop. ❤️ |
On partner form, tick "Force Worker" box to set this partner
as a worker even if they are not an effective cooperator.
Checklist before approval