fix: 0005/08 lesson update

Author: zebateira

src/tutorials/0005-regular-files-api/08.js

@@ -1,5 +1,9 @@
+import all from 'it-all'
+
+import utils from '../utils'
+
 const validate = async (result, ipfs) => {
-  const expectedResult = await ipfs.get('QmcmnUvVV31txDfAddgAaNcNKbrtC2rC9FvkJphNWyM7gy')
+  const expectedResult = await all(ipfs.get('QmcmnUvVV31txDfAddgAaNcNKbrtC2rC9FvkJphNWyM7gy'))
 
   if (!result) {
     return {
@@ -26,7 +30,7 @@ const validate = async (result, ipfs) => {
   }
 
   let isStructureValid = result.every((elem) => {
-    if (elem.hash === undefined || typeof elem.hash !== 'string') return false
+    if (elem.cid === undefined || typeof elem.cid !== 'object') return false
     if (elem.path === undefined || typeof elem.path !== 'string') return false
     if (elem.name === undefined || typeof elem.name !== 'string') return false
     if (elem.depth === undefined || typeof elem.depth !== 'number') return false
@@ -56,33 +60,37 @@ const validate = async (result, ipfs) => {
     return {
       success: "Congratulations! You've completed this series of lessons!",
       logDesc: 'Below is the result of calling the `get` method on the top-level directory. (Normally the results would be much more dense because of the buffered file contents included, but we intentionally created tiny text files to limit this effect.)' +
-              "\n\n Notice that because we created these files using `{ wrapWithDirectory: true }`, each item's `path` is defined here by the top-level directory's CID plus the item's relative path, and each file or subdirectory has a human-readable `name`. Only the top-level directory itself has a `path` value that matches its `hash` and `name`, all of which are identical CIDs.",
-      log: result
+              "\n\n Notice that because we created these files using `{ wrapWithDirectory: true }`, each item's `path` is defined here by the top-level directory's CID plus the item's relative path, and each file or subdirectory has a human-readable `name`. Only the top-level directory itself has a `path` value that matches its `cid` and `name`, all of which are identical CIDs.",
+      log: result.map(utils.format.ipfsObject)
     }
   } else {
     return { fail: `Something seems to be wrong. Please click "Reset Code" and try again, taking another look at the instructions and editing only the portion of code indicated. Feeling really stuck? You can click "View Solution" to see our suggested code.` }
   }
 }
 
 const code = `/* global ipfs */
+const all = require('it-all')
+
 const run = async () => {
-  let result = // your code here
+  let result = await all() // your code here
 
   return result
 }
 return run
 `
 
 const solution = `/* global ipfs */
+const all = require('it-all')
+
 const run = async () => {
-  let result = await ipfs.get('QmcmnUvVV31txDfAddgAaNcNKbrtC2rC9FvkJphNWyM7gy')
+  let result = await all(ipfs.get('QmcmnUvVV31txDfAddgAaNcNKbrtC2rC9FvkJphNWyM7gy'))
 
   return result
 }
 return run
 `
 
-const modules = { cids: require('cids') }
+const modules = { 'it-all': require('it-all') }
 
 const options = {
   overrideErrors: true,

src/tutorials/0005-regular-files-api/08.md

@@ -3,10 +3,10 @@
     type: "code"
 ---
 
-Need to know more about an IPFS file or directory beyond just its contents? Whereas `cat` retrieves just the buffered content of a file, we can access addtional metadata about a file or directory by calling the `get` method like so:
+Need to know more about an IPFS file or directory beyond just its contents? Whereas `cat` retrieves just the buffered content of a file, we can access additional metadata about a file or directory by calling the `get` method like so:
 
 ```javascript
-await ipfs.get(ipfsPath)
+ipfs.get(ipfsPath)
 ```
 
 The result is an array of objects, one per file or directory, with the following structure: