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
Copy file name to clipboardExpand all lines: guides/v3.4.0/routing/query-params.md
+5Lines changed: 5 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -11,6 +11,11 @@ into the URL that can't otherwise fit into the _path_ of the URL (i.e.
11
11
everything to the left of the `?`). Common use cases for query params include
12
12
representing the current page number in a paginated collection, filter criteria, or sorting criteria.
13
13
14
+
In web development, query parameters are used within a URL as described above but can also be used
15
+
in API requests that retrieve data. Ember treats these as _two_ different concepts. This section
16
+
describes how routing query parameters are used in Ember. See [finding records](../../models/finding-records/#toc_querying-for-multiple-records) to see how query parameters are
17
+
applied to API requests in Ember Data.
18
+
14
19
### Specifying Query Parameters
15
20
16
21
Query params are declared on route-driven controllers. For example, to
0 commit comments