-
Notifications
You must be signed in to change notification settings - Fork 258
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
chore: deprecate and remove support for the async graphQL engine #3128
Comments
/bounty $50 |
💎 $50 bounty • Tailcall Inc.Steps to solve:
🙏 Thank you for contributing to tailcallhq/tailcall!
|
/attempt #3128
|
@laststylebender14 @tusharmath, what should be done about parts which depend on A few examples:
|
@dekkku: Reminder that in 1 days the bounty will become up for grabs, so please submit a pull request before then 🙏 |
Remove them if they aren't being used. |
I think they're being used. Should be kept? |
Delete if there is an option to delete, otherwise there is no real option. |
@ologbonowiwi we still use some models from async graphql, like ConstValue etc. so try to clean up as much as possible. |
@imperivox: Reminder that in 1 days the bounty will become up for grabs, so please submit a pull request before then 🙏 |
The bounty is up for grabs! Everyone is welcome to |
/attempt #3128
|
@mehul-m-prajapati: Reminder that in 1 days the bounty will become up for grabs, so please submit a pull request before then 🙏 |
The bounty is up for grabs! Everyone is welcome to |
Currently, Tailcall supports two execution engines:
enableJIT: false
.We plan to remove support for the Async GraphQL Engine, focusing solely on the JIT Engine for performance and maintainability.
Tasks:
The text was updated successfully, but these errors were encountered: