feat!: add initial support for query parameters to exploreDirectory method #94
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As currently discussed in w3c/wot-scripting-api#528, this PR adds initial experimental support for the three query parameters
offset
,limit
, andformat
to theexploreDirectory
method.At the moment only the
format
valuearray
is supported, with the valuecollection
left open for a follow-up PR. While implementing, however, I noticed that the current approach does not allow for an elegant passing of thenext
links (from the HTTP response headers) to the upper layers of the library.Not only in the context of
dart_wot
but also fornode-wot
we could therefore discuss expanding theContent
class/interface to be able to pass this information alongside the payload data. However, there is probably some discussion needed to do this in a protocol-agnostic manner.