@@ -28,7 +28,7 @@ export function createStore () {
28
28
},
29
29
actions: {
30
30
fetchItem ({ commit }, id ) {
31
- // return the Promise via store.dispatch() so that we know
31
+ // return the Promise via ` store.dispatch()` so that we know
32
32
// when the data has been fetched
33
33
return fetchItem (id).then (item => {
34
34
commit (' setItem' , { id, item })
@@ -125,7 +125,7 @@ export default context => {
125
125
reject ({ code: 404 })
126
126
}
127
127
128
- // call asyncData() on all matched route components
128
+ // call ` asyncData()` on all matched route components
129
129
Promise .all (matchedComponents .map (Component => {
130
130
if (Component .asyncData ) {
131
131
return Component .asyncData ({
@@ -178,7 +178,7 @@ On the client, there are two different approaches for handling data fetching:
178
178
router .onReady (() => {
179
179
// Add router hook for handling asyncData.
180
180
// Doing it after initial route is resolved so that we don't double-fetch
181
- // the data that we already have. Using router.beforeResolve() so that all
181
+ // the data that we already have. Using ` router.beforeResolve()` so that all
182
182
// async components are resolved.
183
183
router .beforeResolve ((to , from , next ) => {
184
184
const matched = router .getMatchedComponents (to)
0 commit comments