Added support for Human-Readable Flattened GraphQL Queries
Summary:
Added Support for Human-Readable Flattened GraphQL Queries.
Sample Usage: curl "http://localhost:8000/api/posts?\$=id,user.name&id=1"
Issue Reference(s):
Fixes #560
/claim #560
Build & Testing:
- [x] I ran
cargo testsuccessfully. - [x] I have run
./lint.sh --mode=fixto fix all linting issues raised by./lint.sh --mode=check.
Checklist:
- [x] I have added relevant unit & integration tests.
- [ ] I have updated the documentation accordingly (if applicable).
- [x] I have performed a self-review of my own code.
@ssddOnTop the url should look like —
Expected
curl "https://example.com/api/user?id=123&$=name,age,address.city,address.state"
Actual
curl "https://example.com/api?user&id=123&$=name,age,address.city,address.state"
ie. the operation name should be part of the route and not the query params.
the operation name should be part of the route and not the query params.
yes I will fix that
But apart from that I think keeping we should give key to the query part i.e. $s and $r part
I think I can remove that part but having some key will be much better to recognize
@tusharmath can you assign someone to drop a review
Action required: PR inactive for 2 days. Status update or closure in 5 days.
Action required: PR inactive for 2 days. Status update or closure in 5 days.
/tip 50$ @ssddOnTop
🎉🎈 @ssddOnTop has been awarded $50! 🎈🎊