[IMP] purchase reports extensibility #25903
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of the issue/feature this PR addresses:
In a custom module, suppose you extend the purchase report template using inherit. Then if you want to add
<tr>tags it's difficult if there is a<tr t-foreach=and you are forced to do a xpath replace.To avoid that, this PR adds the same trick as sale report.
Current behavior before PR:
Purchase reports lack some extensibility.
Desired behavior after PR is merged:
Extensibility of purchase reports are improved.
--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr