Open JKRhb opened 9 months ago
Should be part of an options
dictionary, each as a named property, as they need to be validated. They can also be part of options
as a separate dictionary with 3 properties, just like we use URI variable also in InteractionOptions as a parsed JSON object.
That needs more work, too. In general, we need to improve handling URI variables from scripts/web API. IMHO we should make the allowed URI variables explicit(ly validated). Otherwise why do we do a web API, we should be fine with plain RESTful communication, using whatever means from scripts (libraries, fetch, etc).
Call 15/01:
While dealing with the implementation of the
exploreDirectory
method, I noticed that thethings
property in the API specification Thing Model defines threeuriVariables
which are currently not accessible via our API (namely the query parametersoffset
,limit
, andformat
).Should we add these three as optional parameters to the method?