Skip to content
New issue

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

Don't expose a new syntax and instead subscribe to API standards #285

Closed
hpoom opened this issue Jul 20, 2016 · 1 comment · May be fixed by qsays/nodal#7, qsays/nodal#8, qsays/nodal#9, qsays/nodal#10 or rx007/nodal#9

Comments

@hpoom
Copy link

hpoom commented Jul 20, 2016

I feel that although the query parameters mapped to the ORM is powerful, instead of copying Django with things like id__gte=3 instead the default out the box for Nodal should be to subscribe to either json:api or HAL as an API standard.

json:api for example would support filtering and pagination in a standard way.

Ideally the API user should be abstracted away from the data store behind the scenes. Most implementations over time will involve doing more than mapping REST to CRUD and will require those using the framework to add increasing business logic between the CRUD operations on the data store and API payload being sent back to the API consumer, making the current method of query parameters not suitable.

@keithwhor
Copy link
Owner

Thanks for the feedback, but I disagree. I want to give front-end developers increasing control over and insight into the way endpoints are implemented. If anything, we're going to be heading moreso in that direction and away from traditional implementations like json:api or HAL.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment