Issue Multiple Services usage about in-memory-web-api HOT 5 CLOSED

All you need to do is add multiple collections to the returned object in the createDb method

createDb() {
  let service1 = [];
  let service2 = [];
  return { service1, service1 }
}

This gives you access to

/app/service1
/app/service1/1
/app/service2
/app/service2/1

I think some people get confused by the syntax in all the example(s)

return { heroes }

This is the same (shorthand) as

return { heroes: heroes }

So each property in the returned object is considered a collection. So if you have multiple collections, just add more properties. Each property is the collection URL. e.g.

return {
  heroes: heroes     // app/heroes
  crises: crises     // app/crises
}

Or the shorthand

return { heroes, crises }

from in-memory-web-api.

The method I mentioned used to work earlier. Anyways, thanks :)

from in-memory-web-api.

This is a solution in case you're looking for one inMemoryDB to rule them all.
Let me complicate things:
We're using ng6 modules and we want each module to be independent from the rest, while having it's own inMemoryDB.
in that case i cannot have multiple collections at the same DB and only the last module is triggered when the app sends a rest call. (each mock service passThruBackaned in case it does not know how to handle).

any suggestions how to handle that?
thanks

from in-memory-web-api.

This is a solution in case you're looking for one inMemoryDB to rule them all.
Let me complicate things:
We're using ng6 modules and we want each module to be independent from the rest, while having it's own inMemoryDB.
in that case i cannot have multiple collections at the same DB and only the last module is triggered when the app sends a rest call. (each mock service passThruBackaned in case it does not know how to handle).

any suggestions how to handle that?
thanks

I have the the same problem. How to have multiple modules each with their own inMemoryDB.

from in-memory-web-api.

Any updates on this issue?

from in-memory-web-api.