@@ -27,24 +27,30 @@ import org.scalatest.matchers.should.Matchers
2727 *
2828 * If we are just reading data, we can make a series of optimizations such as:
2929 *
30- * - batching requests to the same data source
31- * - requesting independent data from different sources in parallel
32- * - caching previously seen results
30+ * - batching requests to the same data source
31+ * - requesting independent data from different sources in parallel
32+ * - caching previously seen results
3333 *
3434 * However, if we mix these optimizations with the code that fetches the data
3535 * we may end up trading clarity for performance. Furthermore, we are
3636 * mixing low-level (optimization) and high-level (business logic with the data
3737 * we read) concerns.
38+ *
3839 * = Installation =
39- *To begin, add the following dependency to your SBT build file:
40- *{{{
41- *"com.47deg" %% "fetch" % "1.2.1"
42- *}}}
43- *Or, if using Scala.js:
44- *{{{
45- *"com.47deg" %%% "fetch" % "1.2.1"
46- *}}}
47- *Now you’ll have Fetch available in both Scala and Scala.js.
40+ *
41+ * To begin, add the following dependency to your SBT build file:
42+ *
43+ * {{{
44+ * "com.47deg" %% "fetch" % "1.2.1"
45+ * }}}
46+ *
47+ * Or, if using Scala.js:
48+ *
49+ * {{{
50+ * "com.47deg" %%% "fetch" % "1.2.1"
51+ * }}}
52+ *
53+ * Now you’ll have Fetch available in both Scala and Scala.js.
4854 *
4955 * = Usage =
5056 *
@@ -68,8 +74,8 @@ import org.scalatest.matchers.should.Matchers
6874 *
6975 * It takes two type parameters:
7076 *
71- * - `Identity`: the identity we want to fetch (a `UserId` if we were fetching users)
72- * - `Result`: the type of the data we retrieve (a `User` if we were fetching users)
77+ * - `Identity`: the identity we want to fetch (a `UserId` if we were fetching users)
78+ * - `Result`: the type of the data we retrieve (a `User` if we were fetching users)
7379 *
7480 * There are two methods: `fetch` and `batch`. `fetch` receives one identity and must return
7581 * a `Concurrent` containing
0 commit comments