Repository navigation
Conversation
The offset is the part of the recurrence that is hardest to picture, so show it rather than describe it: a table of worked examples for one March period, pre-paid and post-paid, positive and negative. Negative values are worth spelling out, since invoicing a month up front is probably the main reason to reach for the field, and nothing says so today. Generated README.rst and index.html are left out on purpose. My local oca-gen-addon-readme rewrites the page title and drops the OCA banner against what 18.0 has committed, and that noise does not belong in your branch.
Author
|
@anthonissen-a Can you please include this updated documentation in your pr OCA#1536? |
anthonissen-a
force-pushed
the
18.0-contract_invoice_offset_v2-aan
branch
5 times, most recently
from
October 20, 2026 10:19
cebc825 to
12be3b0
Compare
|
Hi @bosd, thanks for your contribution. I cherry-picked your commit into my PR https://github.com/OCA/contract/pull/1536/commits, so I can close this one. |
This file contains hidden or 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.
Adds a readme section for the new invoicing offset, aimed at the people who have to configure it rather than read the code.
The offset is the part of the recurrence that is hardest to picture, so it shows rather than describes: a table of worked examples for one March period, pre-paid and post-paid, positive and negative.
Negative values get their own sentence, since invoicing a month up front is probably the main reason anyone reaches for the field and nothing currently says it is possible.