We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
This is a nice-to-have for 1.0.
As a prerequisite, we should add a soft convention for naming indexes, e.g. as '$<index_name>`, then we can do:
/posts?by=time&first=10&fields=slug,title,at,authors(first:1,name,avatar) should become:
/posts?by=time&first=10&fields=slug,title,at,authors(first:1,name,avatar)
{ 'posts$time': [ { first: 10 }, { slug: 1, title: 1, at: 1, authors: [ { first: 1}, { name: 1, avatar: 1 } ] } ] }
GET /posts/123?fields=slug,title,at,author(name,avatar) should become:
GET /posts/123?fields=slug,title,at,author(name,avatar)
{ 'posts': { 123: { slug: 1, title: 1, at: 1, author: { name: 1, avatar: 1 } } } }
The text was updated successfully, but these errors were encountered:
This change should be in common/encode/url.js.
common/encode/url.js
Sorry, something went wrong.
No branches or pull requests
This is a nice-to-have for 1.0.
As a prerequisite, we should add a soft convention for naming indexes, e.g. as '$<index_name>`, then we can do:
/posts?by=time&first=10&fields=slug,title,at,authors(first:1,name,avatar)
should become:GET /posts/123?fields=slug,title,at,author(name,avatar)
should become:The text was updated successfully, but these errors were encountered: