-
Notifications
You must be signed in to change notification settings - Fork 69
Update declaration payload to match FieldValue
#1138
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
Conversation
|
Oops! Looks like you forgot to update the changelog. When updating CHANGELOG.md, please consider the following:
|
Zangetsu101
left a comment
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.
Let's take another look at the address values, the others look fine
| country: 'FAR', | ||
| addressType: 'DOMESTIC', | ||
| province: '05cbe3a1-9020-47bd-b558-807607c2f119', | ||
| district: 'afaead2b-7ef5-4adb-b4bf-3d2b8437c284', |
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.
Shouldn't the equivalent for this be administrativeAread: 'afaead2b-7ef5-4adb-b4bf-3d2b8437c284'
* fix: Missed conditions on key * Update declaration payload to match `FieldValue` (#1138) * update toolkit * fix: update test data * fix: update toolkit * update toolkit * update toolkit(#a29215b) * fix: add admin area in test data address * Upgrade traefik to 2.11 Fixed Docker API version issue --------- Co-authored-by: Vadym Mudryi <[email protected]> Co-authored-by: Md. Ashikul Alam <[email protected]> Co-authored-by: Barry Dwyer <[email protected]> Co-authored-by: Barry Dwyer <[email protected]>
Note
Currently, we do not run e2e tests as a check on
opencrvs-countryconfig-repo PRs. Please ensure your PR doesn't break any e2e tests.One method for doing this is to open a PR with these changes to
opencrvs-farajalandas well, and see if the PR check passes there.Description
Clearly describe what has been changed. Include relevant context or background.
Explain how the issue was fixed (if applicable) and the root cause.
Link this pull request to the GitHub issue (and optionally name the branch
ocrvs-<issue #>)Checklist