Feat/CC-2559: Save sold land filter option to database #1439
Conversation
This file contains 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
|
Branch name will need to be changed from cc-259 to roe-2559. |
mwejuli-ch
force-pushed
the
feat/cc-2559/save-sold-land-filter-option-to-database
branch
from
c780041
to
99e6f32
Compare
mwestacott
reviewed
Jul 5, 2024
…DIS_removal flag is turned on
…ing or updating an overseas entity
…tity when saving OE name
mwejuli-ch
force-pushed
the
feat/cc-2559/save-sold-land-filter-option-to-database
branch
from
99e6f32
to
0ab0482
Compare
mwejuli-ch
deleted the
feat/cc-2559/save-sold-land-filter-option-to-database
branch
|
@mwestacott - This PR was automatically closed after renaming in GitHub. Looks like there's no way of keeping the same PR after a branch rename. The new PR is now here |
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
https://companieshouse.atlassian.net/browse/ROE-2559
Change description
getApplicationDatamethod to fetch data from APIWork checklist
Merge instructions
We are committed to keeping commit history clean, consistent and linear. To achieve this, 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.