You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One thing that seems to throw beginners is how to specify an alternative root to use for their data structure, as all of our examples show just pointing at data.
The obvious example is to show that instead of pointing at a data object, you could point to data.foo.bar.
Some other projects make this easier to specify by having a root property that you can define, though I'm not convinced we really need that, but I mention it as some people coming from other projects look for the dstore equivalent.
The text was updated successfully, but these errors were encountered:
Given that people often have to work with services they don't have direct control over, being able to tell Request a property to look for data in, as well as an alternative property other than total (which is currently hard-coded) to look for a total number of results in, would be pretty useful. As it is, you'd currently have to either hook up a request provider or do some onerous dancing around with extending _request to accomplish it.
I could add this as a separate issue / feature request, but it's directly related to the documentation being asked for - and basically my TL;DR is it'd be easier to document if we made it easier to actually do, first.
One thing that seems to throw beginners is how to specify an alternative root to use for their data structure, as all of our examples show just pointing at data.
The obvious example is to show that instead of pointing at a data object, you could point to data.foo.bar.
Some other projects make this easier to specify by having a root property that you can define, though I'm not convinced we really need that, but I mention it as some people coming from other projects look for the dstore equivalent.
The text was updated successfully, but these errors were encountered: