You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When a request is made for an unknown resource type, the server returns the resource types that it does know how to handle. When it does so, "List" is shown as "ListResource", which can (and already has) mislead someone trying to debug the error, especially if they then try to request a ListResource (which doesn't exist).
To Reproduce
Steps to reproduce the behavior:
Make a GET request to any invalid resource, like GET /Abcdefgh/1326.
See that "ListResource" is in the error message.
Expected behavior
The "List" resource is correctly shown as "List" in the list of resource types.
Screenshots
Environment:
HAPI FHIR Version: 7.3.0-SNAPSHOT
Additional context
Fix is ready and incoming.
I believe that this happens specifically with "List" because List is already a type in the Java standard library, so the resource class for "List" is named differently.
The text was updated successfully, but these errors were encountered:
…source types (#5875)
* A solution, but perhaps not the best one
* Make behavior more robust and extendable. Fixes#5874
* Apply spotless
* Add changelog
* 😅
* Add unit test
* Get name from context instead of hard-coding remapping
Describe the bug
When a request is made for an unknown resource type, the server returns the resource types that it does know how to handle. When it does so, "List" is shown as "ListResource", which can (and already has) mislead someone trying to debug the error, especially if they then try to request a
ListResource
(which doesn't exist).To Reproduce
Steps to reproduce the behavior:
GET /Abcdefgh/1326
.Expected behavior
The "List" resource is correctly shown as "List" in the list of resource types.
Screenshots
Environment:
Additional context
Fix is ready and incoming.
I believe that this happens specifically with "List" because
List
is already a type in the Java standard library, so the resource class for "List" is named differently.The text was updated successfully, but these errors were encountered: