Refactor/patch dto #213
Open
Refactor/patch dto #213
Conversation
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
|
CI: Security warnings found! |
1 similar comment
|
CI: Security warnings found! |
|
CI: Security warnings found! |
markpit
approved these changes
Aug 29, 2025
markpit
reviewed
Aug 29, 2025
...v/companieshouse/limitedpartnershipsapi/model/partnership/dto/LimitedPartnershipDataDto.java
Show resolved
Hide resolved
|
CI: Security warnings found! |
markpit
approved these changes
Aug 29, 2025
markpit
approved these changes
Aug 29, 2025
|
|
CI: Security warnings found! |
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.
JIRA link
N/A
Change description
remove patch dto and rename data models
Work checklist
Pull request checklist
An exhaustive list of peer review checks can be read here
Merge instructions
We are committed to keeping commit history clean, consistent and linear. To achieve this commit should be structured as follows:
and contain the following structural elements:
BREAKING CHANGE:introduces a breaking API change (correlating with MAJOR in semantic versioning). A BREAKING CHANGE can be part of commits of any type,fix:andfeat:are allowed, for examplebuild:,chore:,ci:,docs:,style:,refactor:,perf:,test:, and others,BREAKING CHANGE: <description>may be provided.