Open norlinhenrik opened 1 month ago
Please avoid plurals in module names, and I would say that this requires a shorter name that summarizes the goal of the module.
I suggested "accounts" and "plans" since they are many2many fields. But I am fine with "account" and "plan".
What would be a good shorter name?
analytic_account_and_plan
?analytic_account_and_plan_mixin
?analytic_mixin_fields
?What about analytic_unfolding_mixin
?
This PR is based on #565. See also PR 1207 for account_financial_report.
account.move.line
new fields:analytic_account_ids
(useful foraccount_financial_report
)analytic_account_names
(introduced in #565)analytic_plan_ids
(introduced by me)analytic_plan_names
(for consistency, but I don't need it)The compute method in
account_financial_report
(AGPL) is written for stored fields, with good performance. The compute method in #565 (LGPL) is written for non-stored fields.QUESTIONS 1) If
account_financial_report
depends on this module foranalytic_account_ids
, will the performance suffer? 2) If no dependency, and both modules introduceanalytic_account_ids
, can both be used in the same database? 3) What should be the module name?