[16.0][ADD] report_qweb_decimal_precision

[yostashiro]

This module allows administrators to define the decimal precision of float fields for QWeb report presentation.

Functionality wise, this basically replaces https://github.com/OCA/reporting-engine/tree/16.0/report_qweb_decimal_place.

Tests need to be added.

Configuration:

Result:

@qrtl

[len-foss]

Code LGTM

Feature is a very nice improvement :-)

[len-foss]

Suggested change

	score = 0
	precision_rec = False
	for dp_qweb_rec in dp_qweb_recs:
	score_rec = dp_qweb_rec._get_score(record)
	if score_rec > score:
	precision_rec = dp_qweb_rec
	precision_rec = max(dp_qweb_recs, default=None, key=lambda r: r._get_score(record))

[yostashiro]

@len-foss Thanks for the suggestion! Updated the code.

[AungKoKoLin1997]

LGTM.

[liuhehe1995]

It worked as expected.
Functional tests were performed.(purchase.order.line/sale.order.line/account.move.line)

[liuhehe1995]

LGTM.

[HviorForgeFlow]

Hello @yostashiro and @AungKoKoLin1997 I can see that both module that you are proposing share similar functionalities. Should I merge this or should we go for #857?

I can see that report_qwebt_field_converter is kind of more generic feature.

Feedback welcome

CC @OCA/reporting-engine-maintainers

[yostashiro]

@HviorForgeFlow Indeed, #857 intends to supersede this PR if it works out nicely. We just haven't gotten around to do a review on that PR, which we will follow up in the coming days.

[HviorForgeFlow]

Ok thanks for your quick feedback, maybe this PR can be closed then.

[HviorForgeFlow]

Pending superseed #857

[github-actions]

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.