Open Dave2526 opened 8 months ago
In my experimentation, it is because filter parameters are apparently expected to be passed directly instead of via the filter_parameters
query arg.
E.g.: date$gte=2024-03-04
works, filter_parameters=date$gte=2024-03-04
doesn't. I still haven't figured out how to pass multiple filter parameters to set a range, date$gte=2024-03-04&date$lte=2024-03-05
doesn't work.
If I can figure this out, I might look into why the Swagger output is wrong.
I opened a MR (https://github.com/nightscout/cgm-remote-monitor/pull/8252) to fix range queries for a single field.
Unfortunately I don't think the current implementation of filter_parameters
in APIv3 is OpenAPI / Swagger compatible so I can't figure out a way to fix it. It can made better by changing the type of filter_parameters
to a string array, with style
set to form
and explode
set to true
. Unfortunately it still prepends filter_parameters
to every parameter so the filters aren't actually applied by the API endpoint.
I'll have to see if I can come up with a way to handle the API as defined in the Swagger definition without breaking the old behavior.
I have opened another MR (#8253) to support filter parameters passed via the filter_parameters
argument to match the behavior described in the current Swagger definition, as well as an update to the Swagger definition which makes it explicit that multiple filter parameters can be passed.
Hi there, i have a Problem with the v3-API swagger... I can get Data from Nightscout, but if I set a filter on The swagger Page I didn´t get any response from it... I tried the given filters and create one by myself, is there an error in it?
Not Working one (without baerer and url):
Body respone:
Working one:
Body response:
To Reproduce Steps to reproduce the behavior: /api3-docs insert bearer auth, Try it out
Expected behavior Get an unempty response
Your setup information