-
Notifications
You must be signed in to change notification settings - Fork 122
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
Add pathBuilder argument to @rest directive #70
Conversation
@HeyHugo: Thank you for submitting a pull request! Before we can merge it, you'll need to sign the Meteor Contributor Agreement here: https://contribute.meteor.com/ |
I updated master with 5kb bundlesize if you want to go-fully green before PR review. Please ping me when you're ready for review here! |
e4af631
to
606d511
Compare
Codecov Report
@@ Coverage Diff @@
## master #70 +/- ##
==========================================
+ Coverage 92.64% 92.82% +0.18%
==========================================
Files 2 2
Lines 231 237 +6
Branches 80 82 +2
==========================================
+ Hits 214 220 +6
Misses 17 17
Continue to review full report at Codecov.
|
606d511
to
46f4cd1
Compare
Ok, you can review now I think @fbartho |
pathBuilder is a user provided function via a graphql variable to build up the path string. A use case it enables is having one or more optional query string parameters e.g: "/items/filter?minPrice=5&maxPrice=20" Here minPrice and maxPrice could be omitted See proposal in apollographql#69 and the problem it solves in apollographql#67
46f4cd1
to
fb8483b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tweaked some docs, and the location of the tests, and the wording of the error message thrown along with adding a bonus test. Will merge into master shortly!
Thanks a ton @HeyHugo ! |
pathBuilder
is a user-provided function via a graphql variable to build up the path string.A use case it enables is having one or more optional query string parameters e.g:
/items/filter?minPrice=5&maxPrice=20
Here minPrice and maxPrice could be omitted
See proposal in #69 and the problem it solves in #67