Query/Paging Brainstorm
by Douglas Campos
Howdy!
As we discussed on our team meeting today, having basic query and pagination support would be cool.
Here are some suggestions, gathered from previous conversations around the topic, and from some BaaS providers in the wild.
Paging:
1) /cars/?limit=10&offset=3
2) /cars/?limit=10&skip=3
Query:
1) /cars/query?color=blue
2) /cars/?query={"color":"red", "owner":"summers"}
3) /cars/?where={"brand":"BMW"}
4) /cars/?query={"engine":{"cylinders": 8}}
5) /cars/?query={"engine":{"cylinders":{"$gt":6}}}
This is not set into stone, just ideas, and I do think that anything above exact matches should go after 1.0
Thoughts?
-- qmx
13 years
[aerogear-controller] Default Error Page
by Daniel Bevenius
Hi all,
I wanted to get some input on what you'd like to see on a default error
page in aerogear-controller. This is the page that a user will see if an
error occurs, and no custom error route has been defined.
I'm attaching a screenshot of what I'm playing with at the moment.
Some thoughts:
1. Should we be showing the stacktrace at all?
2. Should we have a button which can be used to display the stacktrace?
Any suggestions are as always most welcome.
Thanks,
/Daniel
13 years, 1 month
