Repository navigation
init_columns no longer flags column names with the same prefix as duplicates - #1155
Open
PieterjanRobbe wants to merge 1 commit into
Open
PieterjanRobbe wants to merge 1 commit into
PieterjanRobbe wants to merge 1 commit into
Conversation
…duplicates The duplicate check used col.startswith(k), so a column like a.b was rejected when a sibling a.bc had already been scanned. Match on the '.' separator instead; true duplicates (ancestor after child) still raise.
This branch has not been deployed
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.
ContribsClient.init_columnscurrently rejects two columns when one name is a prefix of the other, for example:If we match on the column name +
.separator instead, we fix the prefix issue and duplicate column names are still rejected.