-
-
Notifications
You must be signed in to change notification settings - Fork 766
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
[16.0] [MIG] account_fiscal_year #1473
[16.0] [MIG] account_fiscal_year #1473
Conversation
* Add contributors to README * try to find a FY start date according to the start date from choosen period * Unable to unlink a date_range with type fiscal_year * `fiscal_year` flag readonly * add menu to date_range under accounting section * remove method on object because it's the same as in file * unable to delete with flag 'fiscal_year' but can delete * clean __openerp__.py * account_fiscal_year version number
[MIG] Migrated module 'account_fiscal_year' to V10
[UPD] Update account_fiscal_year.pot
Update translation files Updated by Update PO files to match POT (msgmerge) hook in Weblate.
This date.range.type in v11 have benn used in some cases. Then, when you migrate, you need to have this data or else delete its xmlid. We think it's better to keep it, because you may want to still use it.
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: account-financial-tools-12.0/account-financial-tools-12.0-account_fiscal_year Translate-URL: https://translation.odoo-community.org/projects/account-financial-tools-12-0/account-financial-tools-12-0-account_fiscal_year/
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: account-financial-tools-13.0/account-financial-tools-13.0-account_fiscal_year Translate-URL: https://translation.odoo-community.org/projects/account-financial-tools-13-0/account-financial-tools-13-0-account_fiscal_year/
Currently translated at 100.0% (20 of 20 strings) Translation: account-financial-tools-14.0/account-financial-tools-14.0-account_fiscal_year Translate-URL: https://translation.odoo-community.org/projects/account-financial-tools-14-0/account-financial-tools-14-0-account_fiscal_year/it/
Currently translated at 80.0% (16 of 20 strings) Translation: account-financial-tools-15.0/account-financial-tools-15.0-account_fiscal_year Translate-URL: https://translation.odoo-community.org/projects/account-financial-tools-15-0/account-financial-tools-15-0-account_fiscal_year/es/
Hey @baimont, thank you for your Pull Request. It looks like some users haven't signed our Contributor License Agreement, yet.
Appreciation of efforts, |
/ocabot migration account_fiscal_year |
Sorry @baimont you are not allowed to mark the addon tobe migrated. To do so you must either have push permissions on the repository, or be a declared maintainer of all modified addons. If you wish to adopt an addon and become it's maintainer, open a pull request to add your GitHub login to the |
/ocabot migration account_fiscal_year |
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.
Not an expert in accounting but here is my review, nothing blocking.
@@ -0,0 +1,127 @@ | |||
# Translation of Odoo Server. |
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.
Should this file be merged into fr.PO? It does not look like France-specific french.
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'm not sure this is the time and place to do this.
OCA uses weblate for translations, right? https://odoo-community.org/resources/translate
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 never took the time to investigate weblate, I guess it is smart about that.
intersection_domain = expression.OR( | ||
[ | ||
intersection_domain_from, | ||
intersection_domain_to, | ||
intersection_domain_contain, | ||
] | ||
) |
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 could be simplified to the last of these three domains
intersection_domain = expression.NOT(
expression.OR([ # fiscal years without intersections
("date_to" < date_from),
("date_from" > date_to)
])
)
# equivalent to (Morgan's Law)
intersection_domain = expression.NOT(
expression.AND([
expression.NOT(("date_to" < date_from)),
expression.NOT("date_from" > date_to)
])
)
# equivalent to
intersection_domain = expression.NOT(
expression.AND([
("date_to" >= date_from),
("date_from" <= date_to),
])
)
but that may not be as human readable (matter of taste, I understand the last one) not the place for these changes.
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 actually had @SimoRubi just in front of me, he favors
intersection_domain = expression.NOT(
expression.OR([ # fiscal years without intersections
("date_to" < date_from),
("date_from" > date_to)
])
)
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.
@SimoRubi is no more active, I talked about it with @robinkeunen and yes I think I did it just for human readability.
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.
@robinkeunen ok to let it this way in this pr then?
if you want to change it you can always open a pr for v14.0
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.
fair enough 👌
d2817fe
to
005211d
Compare
Hi @robinkeunen, thanks for your review! I adapted the code or answered to your comments. |
This PR has the |
/ocabot merge patch |
Hey, thanks for contributing! Proceeding to merge this for you. |
Congratulations, your PR was merged at 0b9ca72. Thanks a lot for contributing to OCA. ❤️ |
Hi @dreispt, This module is merged, however the translations are locked: Can I know why? Thanks in advance, |
#1472