FIX Rang of lines in contracts - #40219
Open
thomas-Ngr wants to merge 1 commit into
Open
Conversation
- Origin import (card.php): use an incremental rang instead of a constant $num+1, avoiding all imported lines sharing the same rang. - Contrat::deleteline(): renumber remaining lines after delete, so a removed line never leaves a permanent gap in the rang sequence.
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
1 participant
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.
FIX Order of lines in a contract
Bug : in some cases, you can't reorder lines of a contract.
Seen from DLB 18.0 up to develop.
To reproduce :
This is due to the
rangof line :The fix recomputes the rang of lines each time a line is deleted.