-
-
Notifications
You must be signed in to change notification settings - Fork 791
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
[MIG] report_py3o: Migration to 15.0 #569
Conversation
phuctranfxvn
commented
Dec 22, 2021
- Standard migration of module report_py3o to support odoo 15
- No extra feature added in this migration
088b581
to
a97c409
Compare
Nice! I believe the |
/ocabot migration report_py3o |
59d613d
to
2e0aedf
Compare
@nilshamerlinck @pedrobaeza @gurneyalex |
@BT-dmontull I don't know much about the status of this migration apart from "it needs reviews". I'm not currently using this addon so I can't go beyond "the migration looks good to me". If you are asking, possibly this means you plan on using the module: could you then install it on a test instance and check that it works and make a review? This would allow me to merge the PR. |
@phuctranfxvn can you rebase your PR? |
@phuctranfxvn again, please rebase to resolve conflicts. |
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: reporting-engine-13.0/reporting-engine-13.0-report_py3o Translate-URL: https://translation.odoo-community.org/projects/reporting-engine-13-0/reporting-engine-13-0-report_py3o/
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: reporting-engine-13.0/reporting-engine-13.0-report_py3o Translate-URL: https://translation.odoo-community.org/projects/reporting-engine-13-0/reporting-engine-13-0-report_py3o/
In v 14.0 time module is already in safe_eval https://github.com/odoo/odoo/blob/14.0/odoo/tools/safe_eval.py#L38 Co-authored-by: mourad-ehm <[email protected]>
Co-authored-by: Alexis de Lattre <[email protected]>
…eport displaying date and time
…d red Co-authored-by: Nils Hamerlinck <[email protected]>
Co-authored-by: Nils Hamerlinck <[email protected]>
Co-authored-by: Nils Hamerlinck <[email protected]>
12edc1e
to
5e54d49
Compare
Hello, sorry for late reply. conflicts resolved. |
</record> | ||
<menuitem | ||
id="py3o_template_configuration_menu" | ||
parent="py3o_config_menu" |
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.
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 think we should just drop this sub-menu entirely and make Py3o Templates be sub-menu of Reporting, which seems just fine?
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.
Sounds good!
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 change is mandatory to can see the Py3o models :/ I clarify that right now it is not possible to access the py3o models from the menu. Too many levels to be able to show itself.
I've tested this PR and it works fine, although the js file naming with |
That's according to the OCA guidelines, for ESLint compatibility. Thanks for testing! Can you approve the PR on the |
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.
Tested and work well on my end 👍 Thanks for the contribution
</record> | ||
<menuitem | ||
id="py3o_template_configuration_menu" | ||
parent="py3o_config_menu" |
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 suggest dropping the sub-menu and we should be good to go
parent="py3o_config_menu" | |
parent="base.reporting_menuitem" |
There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days. |
ping @phuctranfxvn |
I go to supersede this PR. |