issue-4987-searchbundle-parts-are-labeled-by-default-as-include-instead-of-match (#4988)

* Default search mode to MATCH when creating SearchBundleEntryParts

* Add changelog

* Use enum name instead of explicit constant

---------

Co-authored-by: juan.marchionatto <juan.marchionatto@smilecdr.com>
This commit is contained in:
jmarchionatto 2023-06-15 10:03:45 -04:00 committed by GitHub
parent c87ff96d5c
commit 048c1f99bb
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 8 additions and 3 deletions

View File

@ -30,10 +30,10 @@ public class SearchBundleEntryParts {
public SearchBundleEntryParts(String theFullUrl, IBaseResource theResource, String theSearchMode) {
myFullUrl = theFullUrl;
myResource = theResource;
if ("match".equalsIgnoreCase(theSearchMode)) {
mySearchMode = BundleEntrySearchModeEnum.MATCH;
} else {
if (BundleEntrySearchModeEnum.INCLUDE.getCode().equalsIgnoreCase(theSearchMode)) {
mySearchMode = BundleEntrySearchModeEnum.INCLUDE;
} else {
mySearchMode = BundleEntrySearchModeEnum.MATCH;
}
}

View File

@ -0,0 +1,5 @@
---
type: fix
issue: 4987
title: "Search bundle entry parts were being created as `INCLUDE` unless explicitly indicated as `MATCH`.
This has been fixed. Now they are created as `MATCH` unless explicitly indicated as `INCLUDE`."