Skip to content

Commit f03d580

Browse files
committed
Highlighted difference between query params (#158)
1 parent fa22969 commit f03d580

File tree

1 file changed

+5
-0
lines changed

1 file changed

+5
-0
lines changed

guides/v3.4.0/routing/query-params.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -11,6 +11,11 @@ into the URL that can't otherwise fit into the _path_ of the URL (i.e.
1111
everything to the left of the `?`). Common use cases for query params include
1212
representing the current page number in a paginated collection, filter criteria, or sorting criteria.
1313

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+
1419
### Specifying Query Parameters
1520

1621
Query params are declared on route-driven controllers. For example, to

0 commit comments

Comments
 (0)