FINERACT-2408: Add entityStatus mapping for SAVING and SHARE entities in the search API#5470
Conversation
|
There's a new ci action for PRs to check that new commits are signed. All committers already have PGP/GPG keys, so just make sure you're also signing commits. You can add this to your ~/.gitconfig (or equivalent) to do it automatically: [commit] Upload your public key to github to make the verified badges green. More info: FINERACT-2177, PR #5431. Hints: 1) try it locally before pushing. 2) have git run it for you: Create .git/hooks/pre-push with: #!/bin/sh Be sure to make that script executable. |
|
Thanks for the heads up! I am setting up GPG signing now and will update the PR with signed commits. |
6a0225f to
2ed023d
Compare
|
I've updated the branch and force-pushed the commits with GPG signing enabled. Thank you for pointing this out! |
2ed023d to
222528f
Compare
|
I have rebased the branch on the latest develop and force-pushed the updated commits. Thank you! |
Description
Implements FINERACT-2408: This PR adds
entityStatusmapping for SAVING and SHARE entities in the search API.The
/v1/searchendpoint returned an emptyentityStatusfor entities of type SAVING and SHARE.This happened because
SearchMapper.mapRow()inSearchReadPlatformServiceImpldid not contain handling for these entity types, so the status defaulted to an emptyEnumOptionData.Solution
Added missing mappings in
SearchMapper.mapRow():For SAVING entity types:
SavingsAccountStatusEnumDatausingSavingsEnumerations.status().EnumOptionDatausing the status data's id, code, and value.For SHARE entity types:
ShareAccountStatusEnumDatausingSharesEnumerations.status().EnumOptionDatausing the status data's id, code, and value.To support this conversion, overloaded
status()methods are introduced inSavingsEnumerationsandSharesEnumerations.Result
Search results for SAVING and SHARE entities now return the correct
entityStatusinstead of empty values.Verification
Before Fix
After Fix
Checklist
Please make sure these boxes are checked before submitting your pull request - thanks!
Your assigned reviewer(s) will follow our guidelines for code reviews.