Code from the "Dependency Injection Basics" episode of Fun Fun Function

episode.js

const assert = require('assert')

function getAnimals(fetch, id) {
  return fetch('http://api.animalfarmgame.com/animals/' + id)
    .then(response => response.json())
    .then(data => data.results[0])
}

describe('getAnimals', () => {
  it('calls fetch with the correct url', () => {
    const fakeFetch = url => {
      assert(
        url ===
        'http://api.animalfarmgame.com/animals/123'
      )
      return new Promise(function(resolve) {

      })
    }
    getAnimals(fakeFetch, 123)
  })

  it('parses the response of fetch correctly', (done) => {
    const fakeFetch = () => {
      return Promise.resolve({
        json: () => Promise.resolve({
          results: [
            { name: 'fluffykins' }
          ]
        })
      })
    }
    getAnimals(fakeFetch, 12345)
      .then(result => {
        assert(result.name === 'fluffykins')
        done()
      })
  })
})

I did some more thingking and this fileStorage.save(fileStream, {user, folder}) strikes me as a bit odd. why do the filesStorage need the user and folder. Is it somehow part of the location that the fileStreamwill bes saved at?

Also there is some asymmetri here. storeDocument gets raw data as arguments, except for the stream object. but the access method userAccess.canWrite(user, folder) takes full-blown object. there might be some answers hidden in this odd relationship.