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
The get() resource proxy method needs to be augmented with some sort of support for passing filters, which will be augmented into a query string. The current API draft dictates the following about filter format:
For example, getting actions with activity ID 1 and any of the locations 1 or 2 would be:
GET /orgs/1/actions?filter=location:1,location:2&filter=activity:1
This would be translated to (location == 1 || location == 2) && activity == 1.
This is what the SDK needs to accommodate. This issue ticket can be used to discuss/draft an interface for passing filters.
The text was updated successfully, but these errors were encountered:
The
get()
resource proxy method needs to be augmented with some sort of support for passing filters, which will be augmented into a query string. The current API draft dictates the following about filter format:This is what the SDK needs to accommodate. This issue ticket can be used to discuss/draft an interface for passing filters.
The text was updated successfully, but these errors were encountered: