-
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
feat: add validation for input types in gRPC #2720
feat: add validation for input types in gRPC #2720
Comments
code wherein we are doing output validation, have added TODO's for input types.
|
/bounty $25 |
💎 $25 bounty • Tailcall Inc.Steps to solve:
🙏 Thank you for contributing to tailcallhq/tailcall!
|
/attempt #2720
|
/attempt #2720 Options |
@akhilender-bongirwar: Reminder that in 1 days the bounty will become up for grabs, so please submit a pull request before then 🙏 |
/attempt #2720 Options |
@swaingotnochill: Reminder that in 1 days the bounty will become up for grabs, so please submit a pull request before then 🙏 |
/attempt #2720
|
Action required: Issue inactive for 30 days. |
Issue closed after 7 days of inactivity. |
/attempt #2720 we can parse and compare the operation.input_type against expected input fields and then we can write unit tests to verify the validation for both valid and invalid input types. Options |
@laststylebender14 is the issue open and unassigned? |
@kananarora1: Reminder that in 1 days the bounty will become up for grabs, so please submit a pull request before then 🙏 |
/attempt #2720 Options |
💡 @HarshMN2345 submitted a pull request that claims the bounty. You can visit your bounty board to reward. |
Presently we only validate the output types for gRPC, add support to validate the input types as well.
Technical Requirements
The text was updated successfully, but these errors were encountered: