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
Ususally elda ItemEndpoints are set to use api:itemTemplate based URI patterns, However, there are unusual cases where an api:selector is used to specifiy a selector intended to return a single value.
However, if the selector fails to return any items, elda 'invents' the URI elda:missingEndpoint as a primary topic for the otherwise empty page.
If api:itemTemplate is used elda either 404s or may return an empty response page depending on the setting of _exceptionIfEmpty.
Please could you alter the behaviour of selector based item endpoints to mirror the behaviour of item template based item end points or at least make such behaviour a configuration option,
Ususally elda
ItemEndpoints
are set to useapi:itemTemplate
based URI patterns, However, there are unusual cases where anapi:selector
is used to specifiy a selector intended to return a single value.However, if the selector fails to return any items, elda 'invents' the URI
elda:missingEndpoint
as a primary topic for the otherwise empty page.If
api:itemTemplate
is used elda either 404s or may return an empty response page depending on the setting of_exceptionIfEmpty
.Please could you alter the behaviour of selector based item endpoints to mirror the behaviour of item template based item end points or at least make such behaviour a configuration option,
Example:
http://landregistry.data.gov.uk/data/hpi/region/shropshire/month/2017-02
compare with
http://landregistry.data.gov.uk/data/hpi/region/shropshire/month/2016-02
The text was updated successfully, but these errors were encountered: