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
We currently only support going through sensor data page-by-page with the prev, next, first, and last links. We should add official support for user-specified ranges with query parameters and templated links. Currently the data link looks like:
If a client requests the URI with the {×tamp__gte,timestamp__lt} part present, we'd just ignore everything in the braces, so non-template-aware clients can continue to treat the link as an opaque string.
We currently only support going through sensor data page-by-page with the
prev
,next
,first
, andlast
links. We should add official support for user-specified ranges with query parameters and templated links. Currently the data link looks like:The proposed new link would be:
This conforms to the IETF RFC for templated URIs.
If a client requests the URI with the
{×tamp__gte,timestamp__lt}
part present, we'd just ignore everything in the braces, so non-template-aware clients can continue to treat the link as an opaque string.We'll also want to add support to
chainclient.py
: ssfrr/chainclient.py#4The text was updated successfully, but these errors were encountered: