Prior to this PR, the way to get the details of a term was to use the show action. The term is identified by appending the term's id to the end of the URL request path in the form:
http://my.app/qa/show/vocab/123
This approach does not work for IDs that are URIs. The slashes in the URI get interpreted as part of the path. The introduction of the fetch action allows the URI to be passed in as a parameter instead of as part of the path.
Prior to this PR, the way to get the details of a term was to use the
show
action. The term is identified by appending the term's id to the end of the URL request path in the form:This approach does not work for IDs that are URIs. The slashes in the URI get interpreted as part of the path. The introduction of the
fetch
action allows the URI to be passed in as a parameter instead of as part of the path.NOTE: The linked data module already uses
fetch
to pass in a URI since almost all IDs are URIs.