-
Notifications
You must be signed in to change notification settings - Fork 214
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
refactor: Enhance implementation of @call
#1285
Comments
@call
@call
I attempted to accomplish this on feat/#846/create-call-operator-via-resolver-with-arg, in case it helps. It's not working, but can be taken inspiration from. |
Can do it after this — #1484 /bounty 150 |
💎 $150 bounty created by tailcallhq 🙏 Thank you for contributing to tailcallhq/tailcall!.
|
/attempt 1285
|
Use the |
@ologbonowiwi Feel free to pick this one up. @ssddOnTop I think you should drop this one since you have a lot on your plate already. |
💡 @ologbonowiwi submitted a pull request that claims the bounty. You can visit your bounty board to reward. |
…thub.com:ologbonowiwi/tailcall into feat/tailcallhq#1285/enhance-call-implementation
…allhq#1285/enhance-call-implementation
…thub.com:ologbonowiwi/tailcall into feat/tailcallhq#1285/enhance-call-implementation
@ologbonowiwi: You've been awarded a $150 bounty by tailcallhq! We'll notify you once it is processed. |
🎉🎈 @ologbonowiwi has been awarded $150! 🎈🎊 |
The current implementation of
call
handles each IO type viz. HTTP, gRPC, GraphQL, and Const, specifically. This means every time we add a new IO, we need to go here and make a change.Proposal
Use
Expression::Push_Args
to set the args for the for thecall
operator. This should make thecall::compile_call
function significantly easier.The text was updated successfully, but these errors were encountered: