Skip to content
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

Closed
wants to merge 112 commits into from

Conversation

phuctranfxvn
Copy link
Contributor

  • Standard migration of module report_py3o to support odoo 15
  • No extra feature added in this migration

@phuctranfxvn phuctranfxvn mentioned this pull request Dec 22, 2021
20 tasks
@phuctranfxvn phuctranfxvn force-pushed the 15.0-mig-report_py3o branch 3 times, most recently from 088b581 to a97c409 Compare December 22, 2021 05:19
@nilshamerlinck
Copy link
Contributor

Nice!

I believe the ci/runbot check could be disabled for this branch, right @gurneyalex ?

@pedrobaeza
Copy link
Member

/ocabot migration report_py3o

@OCA-git-bot OCA-git-bot added this to the 15.0 milestone Jan 24, 2022
@phuctranfxvn phuctranfxvn force-pushed the 15.0-mig-report_py3o branch 2 times, most recently from 59d613d to 2e0aedf Compare February 1, 2022 14:30
@BT-dmontull
Copy link

@nilshamerlinck @pedrobaeza @gurneyalex
Does anyone know the status of this migration? it seems to be giving error in a check that it is no longer used.
thanks

@gurneyalex
Copy link
Member

@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.

@gurneyalex
Copy link
Member

@phuctranfxvn can you rebase your PR?

BT-dmontull added a commit to brain-tec/reporting-engine that referenced this pull request Apr 7, 2022
@StefanRijnhart
Copy link
Member

@phuctranfxvn again, please rebase to resolve conflicts.

sbidoul and others added 17 commits May 15, 2022 22:01
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/
@phuctranfxvn
Copy link
Contributor Author

@phuctranfxvn again, please rebase to resolve conflicts.

Hello, sorry for late reply. conflicts resolved.

</record>
<menuitem
id="py3o_template_configuration_menu"
parent="py3o_config_menu"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't see this template submenu in runboat (as user admin):

image

The same template menu does appear in the 14.0 runboat of this project:

image

Do you know why?

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?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sounds good!

Copy link
Member

@Tardo Tardo Feb 8, 2023

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.

@hoangtrann
Copy link

I've tested this PR and it works fine, although the js file naming with esm is a bit off from other sources

@StefanRijnhart
Copy link
Member

StefanRijnhart commented Oct 4, 2022

I've tested this PR and it works fine, although the js file naming with esm is a bit off from other sources

That's according to the OCA guidelines, for ESLint compatibility.

Thanks for testing! Can you approve the PR on the Files changed tab?

Copy link

@hoangtrann hoangtrann left a 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"

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

Suggested change
parent="py3o_config_menu"
parent="base.reporting_menuitem"

@github-actions
Copy link

github-actions bot commented Feb 5, 2023

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.
If you want this PR to never become stale, please ask a PSC member to apply the "no stale" label.

@github-actions github-actions bot added the stale PR/Issue without recent activity, it'll be soon closed automatically. label Feb 5, 2023
@github-actions github-actions bot closed this Mar 12, 2023
@Tardo
Copy link
Member

Tardo commented Mar 17, 2023

ping @phuctranfxvn

@Tardo
Copy link
Member

Tardo commented Mar 24, 2023

I go to supersede this PR.

@Tardo Tardo mentioned this pull request Mar 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved stale PR/Issue without recent activity, it'll be soon closed automatically.
Projects
None yet
Development

Successfully merging this pull request may close these issues.