Conversation
…ates unique constraint
…lue violates unique constraint" This reverts commit 452597d.
…ates unique constraint
…ates unique constraint
…ates unique constraint
…coping (#1818) Adds a functional regression guard for the import fix: a definition that reuses the same FixedList ID across two case types (each tagged with CaseTypeID) must import successfully (no duplicate field-type reference / unique_field_type_reference_version_jurisdiction violation). - F-126.feature / S-126.1 (extends Import_Base_data, expects 201) mirroring the F-106/F-112 'new import column' BEFTA pattern. - Self-contained fixture CCD_6594_FixedList_CaseType.xlsx (AUTOTEST1: same list id 'coCourtList' under AAT and MAPPER, CaseTypeID populated).
hmcts-jenkins-a-to-c
Bot
added
ns:ccd
prd:ccd
rel:ccd-definition-store-api-pr-1817
labels
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
2 participants
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.
Before creating a pull request make sure that:
keep-helmlabel has been added, if the helm release should be persisted after a successful buildPlease remove this line and everything above and fill the following sections:
JIRA link (if applicable)
Change description
Does this PR introduce a breaking change? (check one with "x")