Custom operation should support more types being passed from URI #75
Comments
|
It's intentional :) there is a todo in the BulkDataClient to pass the joined list. |
|
I really think we should just expand the set of supported types that come in from the URL. Its not a bulk issue; just a limitation of current operation framework impl. Will have PR shortly. |
lmsurpre
added a commit
that referenced
this issue
Sep 15, 2019
This adds support for all primitive types except for "base64" and "markdown". Still needs test. Signed-off-by: lmsurpre <lmsurpre@us.ibm.com>
|
I don't think this is really blocked by #55. I just need to add some tests and then I'll close it out. |
|
was not the intent to block - rather link the two |
|
yeah, i wish they had a "related to". all you can really do then is just mentioned the issue #s in comments. |
lmsurpre
added a commit
that referenced
this issue
Sep 19, 2019
* 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>
lmsurpre
added a commit
that referenced
this issue
Sep 19, 2019
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>
lmsurpre
added a commit
that referenced
this issue
Sep 19, 2019
…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>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
While trying to invoke $export operation via GET, it complains that we can't process an input parameter of type instant.
To Reproduce
Invoke export with a request like this:
{{http}}://{{host}}:{{port}}/{{basePath}}/$export?_outputFormat=application/fhir+ndjson&_since=2019-01-01T08:21:26.94-04:00&_type=PatientAdditional context
Spec says we should support passing of "primitive" types via URL.
The text was updated successfully, but these errors were encountered: