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
"description": "If queries support ad-hoc filtering of resources through flexible predicates, they do so via the where query\nparameter that accepts a single (possibly compound) predicate to determine whether a specific resource\nrepresentation should be included in the result.\n\nThe structure of predicates and the names of the fields follow the structure and naming of the fields in the\ndocumented response representation of the query results.\n\nExamples of predicates:\n\n // Compare a field's value to a given value\n name = \"Peter\"\n age < 42\n age > 42\n age <= 42\n age >= 42\n age <> 42\n\n // Combine any two conditional expressions in a logical conjunction / disjunction\n name = \"Peter\" and age < 42\n name = \"Peter\" or age < 42\n\n // Negate any other conditional expression\n not (name = \"Peter\" and age < 42)\n\n // Check whether a field's value is or is not contained in\n // a specified set of values.\n age in (42, 43, 44)\n age not in (42, 43, 44)\n\n // Check whether an array contains all or any of a set of values\n tags contains all (\"a\", \"b\", \"c\")\n tags contains any (\"a\", \"b\", \"c\")\n\n // Check whether an array is empty\n tags is empty\n\n // Check whether a field exists & has a non-null value\n name is defined\n name is not defined\n\n // Descend into nested objects\n dog(age < 7 and name = \"Beethoven\")\n\n // Descend into nested arrays of objects\n cities(zip > 10000 and zip < 20000)\n\nA query endpoint usually restricts predicates to only be allowed on a specified subset of a resource\nrepresentation's fields. The documentation of the endpoint will therefore list fields that can be used\nfor constructing predicates.\n\nIf multiple predicates are specified via multiple where query parameters, the individual predicates are\ncombined in a logical conjunction, just as if they had been specified in a single where query parameter\nand combined with and.\n\nNote: The encoding of the predicates is UTF-8 and the predicate must be URL-encoded in the HTTP request.\n",
39763
+
"type": "string",
39764
+
"in": "query",
39765
+
"name": "where"
39766
+
},
39767
+
{
39768
+
"description": "A query endpoint that supports sorting does so through the sort query parameter. The provided value must be\na valid sort expression. The default sort direction is ASC. The allowed sort paths are typically listed on\nthe specific query endpoints.\n\nHere are some examples of sort expressions:\n\n name desc\n dog.age asc\n\nIf multiple sort expressions are specified via multiple sort parameters, they are combined into a composed\nsort where the results are first sorted by the first expression, followed by equal values being sorted\naccording to the second expression, and so on.\n\nNote: The sorting is case sensitive.\n",
0 commit comments