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
[12.0][ADD] hr_timesheet_task_domain: task domain depends on project #180
[12.0][ADD] hr_timesheet_task_domain: task domain depends on project #180
Conversation
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.
@alexey-pelykh I'm not a fan of this kind of code where we ckeck if an addon is installed to constrain in a way or an other the logic. I personally prefer glue addons. Nevertheless I'll not block this PR.
What do you think about the proposed optimization?
abb1260
to
10444d0
Compare
@lmignon thanks for your feedback! Likewise, I don't like duck-typing or duck-programming, yet this particular case this is a trade-off, since a separate module to add 2 lines of check would be quite significant overkill, IMO |
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.
Thank you @alexey-pelykh LGTM (code review only)
5f79abf
to
b45541a
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.
The flow we have in project_timesheet_time_control
is that all the tasks are shown if no project selected, and only opened ones if a project is selected.
b45541a
to
ae03d9a
Compare
@pedrobaeza right, this module has the same approach and is part of #139 #179 and OCA/project#474 |
This PR has the |
A complimentary module to #139 in order to provide a seamless substitute for OCA/project#447