Kiryl Mialeshka

Results 62 comments of Kiryl Mialeshka

fix(grpc): remove validation for grpc

Is there any actual reason for fields not to convert to camelCase on generation? I got the issues for type names and names collisions for them, but fields are scoped...

fix(grpc): remove validation for grpc

Overall, I think we should try to follow [GraphQL Naming Convention](https://www.apollographql.com/docs/technotes/TN0002-schema-naming-conventions/) when generating config so linting for it won't fail

fix(grpc): remove validation for grpc

In https://github.com/tailcallhq/tailcall/pull/1895 generation has changed and validation should work as expected

refactor(init): improve/simplify CLI experience

@ologbonowiwi please, update the branch and fix conflicts

Create a `@call` operator

@Khalid6468 could you please share your status on this? If it's not much it's might be better to reassign to @ologbonowiwi that made some progress on this

feat(auth): Auth with jwt support

> Can you resolve the conflicts done

Create an expression for caching

was done previously in https://github.com/tailcallhq/tailcall/pull/1078

feat: type checking for composition with `@graphQL`

Thank you for the pr. Could you describe a little more about the approach you've chosen? I see that we need to define schema once again for the upstream, but...

Stackoverflow Errors on recursive types

assigning back to @A-N-uraag since they have work in progress on it

Support multiple upstream settings

> @meskill Proposed solution, let me know your thoughts. > > 1. If only a single `upstream` is specified, it will be the default, and things will work as before....