We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
To reduce the code complexity and the load on the DS backend, can I propose parameterized combinators as a future enhancement?
e.g.
[ { "endpoint": "rumpel/locations", "filters": [ { "field": "data.locations.timestamp", "transformation": { "transformation": "datetimeExtract", "part": "hour" }, "operator": { "operator": "between", "lower": "$lower", "upper": "$upper" } } ] } ]
The call to get the result would then be: GET /api/v2.6/combinator/$COMBINATOR_NAME?lower=7&upper=9
GET /api/v2.6/combinator/$COMBINATOR_NAME?lower=7&upper=9
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Suggestion from Chris Pointon
To reduce the code complexity and the load on the DS backend, can I propose parameterized combinators as a future enhancement?
e.g.
The call to get the result would then be:
GET /api/v2.6/combinator/$COMBINATOR_NAME?lower=7&upper=9
The text was updated successfully, but these errors were encountered: