@@ -28,7 +28,7 @@ export function createStore () {
2828 },
2929 actions: {
3030 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
3232 // when the data has been fetched
3333 return fetchItem (id).then (item => {
3434 commit (' setItem' , { id, item })
@@ -125,7 +125,7 @@ export default context => {
125125 reject ({ code: 404 })
126126 }
127127
128- // call asyncData() on all matched route components
128+ // call ` asyncData()` on all matched route components
129129 Promise .all (matchedComponents .map (Component => {
130130 if (Component .asyncData ) {
131131 return Component .asyncData ({
@@ -178,7 +178,7 @@ On the client, there are two different approaches for handling data fetching:
178178 router .onReady (() => {
179179 // Add router hook for handling asyncData.
180180 // 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
182182 // async components are resolved.
183183 router .beforeResolve ((to , from , next ) => {
184184 const matched = router .getMatchedComponents (to)
0 commit comments