8000 [18.0][MIG] analytic_brand: Migration to 18.0 by BhaveshHeliconia · Pull Request #231 · OCA/brand · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

[18.0][MIG] analytic_brand: Migration to 18.0 #231

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

Merged
merged 23 commits into from
Apr 24, 2025

Conversation

BhaveshHeliconia
Copy link
Contributor
@BhaveshHeliconia BhaveshHeliconia commented Feb 11, 2025

sbejaoui and others added 22 commits February 11, 2025 10:22
[UPD] README.rst

[FIX] Fixed travis.
[UPD] Update analytic_brand.pot
Currently translated at 100.0% (2 of 2 strings)

Translation: brand-15.0/brand-15.0-analytic_brand
Translate-URL: https://translation.odoo-community.org/projects/brand-15-0/brand-15-0-analytic_brand/es/
Currently translated at 100.0% (2 of 2 strings)

Translation: brand-17.0/brand-17.0-analytic_brand
Translate-URL: https://translation.odoo-community.org/projects/brand-17-0/brand-17-0-analytic_brand/it/
@max3903 max3903 added this to the 18.0 milestone Apr 9, 2025
@bosd
Copy link
Contributor
bosd commented Apr 9, 2025

@BhaveshHeliconia Can you remove the test dependencies on this one?

@BhaveshHeliconia
Copy link
Contributor Author

@bosd, I removed test file.Please review the PR when you get a chance.

Copy link
Contributor
@bosd bosd left a comment

Choose a reason for hiding this comment

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

The readme / usage instructions could be improved on this one.

  • Mention the user has to have analytic account acces rights.
  • Go to Configuration -> Settings -> Brands
    Select a brand and setup an analytic account.

Please drop the last 2 commits. They do'nt have to be in the modules history.

Copy link
Contributor
@marielejeune marielejeune left a comment

Choose a reason for hiding this comment

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

LGTM

# Create a plan (assuming a Plan model exists and is required)
self.plan = self.env["account.analytic.plan"].create(
{
"name": "Test Plan", # Ensure this is the correct model and fields
Copy link
Contributor

Choose a reason for hiding this comment

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

What is this comment for?

8000
self.analytic_account = self.env["account.analytic.account"].create(
{
"name": "Test Analytic Account",
"plan_id": self.plan.id, # Ensure plan_id is set
Copy link
Contributor

Choose a reason for hiding this comment

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

What is this comment for?

@BhaveshHeliconia BhaveshHeliconia force-pushed the 18.0-mig-analytic_brand branch from ebbd751 to 5d1d5b1 Compare April 15, 2025 06:02
@BhaveshHeliconia
Copy link
Contributor Author

@bosd, Apologies, this was added by mistake. I’ll make sure to avoid it in the future.Please Review.

@bosd
Copy link
Contributor
bosd commented Apr 15, 2025

@bosd, Apologies, this was added by mistake. I’ll make sure to avoid it in the future.Please Review.

The test-requirements.txt was once needed to pass the test. When the mentioned modules were not merged.
Since they are merged, the test-requirements.txt file can be empty.
Like you did.

But the two commits for editing that file are still in the history.
Can you please remove them?
You can do this from the terminal:

$ git rebase -i HEAD~2

Your text editor will open and show you the last 2 commits.
You can replace the words pick with the letter d.
sve and close the editor. Then invoika a
$ git push --force-with-lease

@BhaveshHeliconia BhaveshHeliconia force-pushed the 18.0-mig-analytic_brand branch from 5d1d5b1 to 2805e20 Compare April 15, 2025 06:54
@BhaveshHeliconia
Copy link
Contributor Author

@bosd Thanks for the suggestions! I updated.

Copy link
Contributor
@marielejeune marielejeune left a comment

Choose a reason for hiding this comment

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

LGTM

@OCA-git-bot
Copy link
Contributor

This PR has the approved label and has been created more than 5 days ago. It should therefore be ready to merge by a maintainer (or a PSC member if the concerned addon has no declared maintainer). 🤖

@marielejeune
Copy link
Contributor

@BhaveshHeliconia @bosd please have a look at #244
I think that replacing analytic account by analytic distribution as Odoo/OCA did at many places can be interesting.

@sbejaoui
Copy link
Contributor

@BhaveshHeliconia @bosd please have a look at #244 I think that replacing analytic account by analytic distribution as Odoo/OCA did at many places can be interesting.

Indeed, replacing the analytic account with a distribution is necessary to stay up to date with Odoo's analytics system.

I will merge this PR as standard migration and keep the improvement in #244

@sbejaoui
Copy link
Contributor

/ocabot merge nobump

@OCA-git-bot
Copy link
Contributor

This PR looks fantastic, let's merge it!
Prepared branch 18.0-ocabot-merge-pr-231-by-sbejaoui-bump-nobump, awaiting test results.

@OCA-git-bot OCA-git-bot merged commit e8986d5 into OCA:18.0 Apr 24, 2025
7 checks passed
@OCA-git-bot
Copy link
Contributor

Congratulations, your PR was merged at cf46350. Thanks a lot for contributing to OCA. ❤️

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0