Open janol77 opened 5 years ago
This is still a problem. From the 4.1.0-SNAPSHOT server at hapi.fhir.org:
{
"name": "near",
"documentation": "Search for locations..."
},
Also, this is not only a problem with the near
search parameter. It appears that this happens for any search parameter whose type is special
. For example, it also happens with this custom search parameter.
This prevents the CapabilityStatement from validating, so it's a pretty serious problem for any testing which expects all resources to be valid.
Describe the bug I have some troubles with conformance report of my R4 fhir server, because in the search parameters section of the Location resource, the search parameter called "near" is missing a mandatory param(type--> in R4 its a special type). i dont now if this is a normal thing beacause the version 3.7 of hapi its still under a dev version,
To Reproduce Steps to reproduce the behavior:
Expected behavior The type in the searchParam its a mandatory value and in this case its a special value
Environment :