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
It would be nice to be able to choose whether a parameter that maps to a SPARQL variable should be a query param or a path param. For example, one may want to turn:
basil/abcdef1234/api?type={type}&term={term}
into something like
basil/abcdef1234/api/{type}/{term}
This obviously means that the Web API parameters would become positional and there should be a way to configure that. I can think of a few ways:
Extend the naming convention with ordering, for example ?_1_type could mean that type is a path parameter that comes before any other.
Extend alias definition to support templating, for example if I want to alias abcdef1234 as search I could define the alias as {type}/search/{term}.
Infer the order from where the variables first appear in the query (my least-favourite option).
The text was updated successfully, but these errors were encountered:
It would be nice to be able to choose whether a parameter that maps to a SPARQL variable should be a query param or a path param. For example, one may want to turn:
into something like
This obviously means that the Web API parameters would become positional and there should be a way to configure that. I can think of a few ways:
?_1_type
could mean thattype
is a path parameter that comes before any other.abcdef1234
assearch
I could define the alias as{type}/search/{term}
.The text was updated successfully, but these errors were encountered: