Now that we have an initial design lets break up the work to get it done!
Special thanks to @sabativi who wrote the version on master to experiment and try out the link! We have a great starting point thanks to you! And to @fbartho who has helped inform the design in a great way and pushed for the project to be built!
If anyone wants to help, please comment with what they want to do!
@rest
RestLink
instead of RestAPILink
endPoint
to be endpoint
endpoint
for the @rest(…
directive, and name it path:
for the server path (without the host).endpoints:
optional parameter for people who have more than one RestLinkcustomFetch:
optional parameter.method:
parameter on rest calls.@export
directiveAlso, join us in the #apollo-link-rest channel on slack!
What would be the smallest thing to start with in terms of contribution effort? I guess something like fetch method
or headers
?
PS: thanks a lot for pushing this project, really exited to see it working! 🙌
@emmenko yeah that would be a great start! You should be able to pull a lot of code from how apollo-link-http works for this!
Let me know if you have any questions, I'm so excited you want to be a part of this project 🎉
Well, I'm glad if I can help somehow. However I don't have the time to fully contribute to this project, so don't expect too much from me 🙏😅
With that said, I'll try to focus on those parts first. Let's see how it goes 🚀
I guess I can also add the credentials
part, it's more or less copy-pasta from the http link 😅
I will work this week on 'support mixed and nested directive usage'.
To do this I will try to rewrite the logic with graphql-anywhere
.
Also, after looking at link-state, we use apollo-utililies
the same way.
Any smaller tasks remaining that I could take a pass at? Looking to contribute, but it looks like most of the tasks in this issue have been completed or are more complex?
@Skovy I didn't get a chance to take on the credentials
part yet. It's a really small task, you can take this over if you'd like 😉
@emmenko cool, I'll take a stab at it! 👍
Closing this ticket, since the remaining issues are separately tracked in the issue db!