-
Notifications
You must be signed in to change notification settings - Fork 157
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
Issue 75 - add tests for invoking custom operation framework with query parms #96
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
lmsurpre
force-pushed
the
issue-75
branch
2 times, most recently
from
September 18, 2019 18:37
62669e0
to
b57515b
Compare
Signed-off-by: Lee Surprenant <lmsurpre@us.ibm.com>
…egration script Signed-off-by: Lee Surprenant <lmsurpre@us.ibm.com>
Signed-off-by: Lee Surprenant <lmsurpre@us.ibm.com>
* Updated MyOperation to accept many optional parameters and return empty response if nothing was passed. * Added test to invoke $hello operation with no body and return empty response. * Added isEmpty helper in FHIRResponse. Signed-off-by: lmsurpre <lmsurpre@us.ibm.com>
Validation now returns warnings and so we should not check for "All OK" but instead just use the response code. Signed-off-by: lmsurpre <lmsurpre@us.ibm.com>
…ery param 1. introduced test for invoking $hello operation with all supported primitive types 2. fixed bug in FHIROperationUtil for missing "id" datatype support 3. enabled FHIROperationTest by default Signed-off-by: Lee Surprenant <lmsurpre@us.ibm.com>
lmsurpre
changed the title
WIP Issue 75 - add tests for invoking custom operation framework with query parms
Issue 75 - add tests for invoking custom operation framework with query parms
Sep 19, 2019
Build and integration tests (including FHIROperationTest) are now working for me:
|
Verified build locally
|
prb112
approved these changes
Sep 19, 2019
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.
LGTM
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.
Code for addressing issue #75 was added in #77 ...
Now we just need to verify its working (beyond the $export operation).
MyOperation
operation. This was accidentally broken from migrating to R4 but no one noticed since the tests aren't integrated into our build.$hello
impl to accept optional params of each primitive type (minus base64Binary and markdown)