Enhancement: Dojo ResourceProvider - Read Many API

[agubler]

Initial resources abstraction to provide mechanism to inject a provider into an application and an API to fetch resources based on the configuration passed.

• Scaffolds the resource package
• Initial getOrRead API - this API either runs the specified function to fetch resources and subsequently returns cached resources
• Pagination support with getOrRead
• next and prev API to work with pagination
• Restful configuration for fetching resources from a remote REST server
• README documentation
• Unit tests

Related to #2

[agubler]

Remove

[agubler]

Keeping this for now as describes the desired data model for resources

[agubler]

This can probably only invalidate on changes to the data path as it's all this API is interested in

[agubler]

Does optimistic make sense as a possible option on reading/fetching resources? Possibly not as we cannot optimistically update the store like we can for update/create/remove

[aciccarello]

Looks interesting @agubler! So is the provider the primary API? Are you able to get other items from the store from a resource provider? Most of the time our providers are combining several different things. A processor factory seems like a more reusable part of this from what I've gathered. Am I thinking about this correctly?

[matt-gadd]

@aciccarello Yeah the primary api is via the Provider. No you won't be able to access other parts from the Store as part of the Resources api (all Store related things are considered opaque in Resources, we are actually likely to factory our own internal Resource Store rather than using the users Store).

[matt-gadd]

when we eventually move this from a Provider to the new more generic meta api composing multiple resources will look like something like this:

render() {
  const todoResource = use(TodoResource);
  const someOtherResource = use(SomeOtherResource);
  const todos = todoResource.getOrRead();
  const [someOther] = someOtherResource.getOrRead();
  return todos.map(todo => (
    <div>
      <div>{someOther.yay}</div>
      <div>{todo.id}</div>
      <div>{todo.title}</div>
      <div>{todo.completed ? "completed" : "incomplete"}</div>
    </div>
  ));
};

[agubler]

closing as this was a POC that will be superseded