-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DFPL-2546 Refuge Address option for Respondent/Other persons Journeys #5755
Conversation
This reverts commit afee204.
This reverts commit afee204.
// Flag for preventing from purging the converted old field value during deserialization if addressKnowV2 is null | ||
@Builder.Default | ||
@Getter(AccessLevel.NONE) | ||
private final boolean isConvertedAddressKnow = false; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this get used? Can see it's also defined on 173
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it won't get serialised to Json, as @Getter(AccessLevel.NONE) mean no getter is generated for this field.
And it is only being used as internal flag when building the object
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oh! right, that one in builder is redundant
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My bad, not that one in the builder, this one is redundant. Just did some simple test, that one in builder is thread safe. so should be fine
* DFPL-2641: Move address known type to the confidential tab * DFPL-2641: Refactor conversion tests, temp dupe function for others as incompatible due to UUIDs for firstOther * DFPL-2641: Fix controller test * DFPL-2641: Fix test - everyone was named James, clashing with new code... * DFPL-2641: Fix test * DFPL-2641: Fix test * DFPL-2641: Fix test
…5796) Co-authored-by: prabhamuthu15 <[email protected]>
JIRA link (if applicable)
https://tools.hmcts.net/jira/browse/DFPL-2546
Change description
Refuge Address option for Respondent/Other persons Journeys.
#5696 Release failed as the pipeline failed to import CCD definition. The ticket was rolled back.
Error message was:
ElasticSearch initialisation exception" mapper [data.hearingDetails.value.others.value.addressKnow] cannot be changed from type [keyword] to [text]
This PR fix the issue by introducing a new field "addressKnowV2" insetad of updating the type of the existing "addressKnow" field
The old field is deprecated, and the application will convert the old field to new field during case data deserialisation.
Does this PR introduce a breaking change? (check one with "x")