You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Let me describe the case to make it clear why I need this. Our company has protobuf-based service, but not grpc.
By use of grpc module I managed to build easily graphql schema. Despite I cannot use directly ( our API cannot decode grpc request ) - I can create a new graphql handler with own resolver.
In that resolver I'm exporting graphql schema, generated with grpc module along with generated TypeScript types.
However what I don't like - is that index.ts contains not only types but also grpc-relevant resolvers.
So in my case those additional lines are not really needed. So having an opportunity to have separately types.d.ts along with index.ts would entirely solve my issue?
Do you think is possible now?
Is it difficult to adjust mesh build command to support this feature?
Thank you!
The text was updated successfully, but these errors were encountered:
Hi!
Let me describe the case to make it clear why I need this. Our company has protobuf-based service, but not grpc.
By use of grpc module I managed to build easily graphql schema. Despite I cannot use directly ( our API cannot decode grpc request ) - I can create a new graphql handler with own resolver.
In that resolver I'm exporting graphql schema, generated with grpc module along with generated TypeScript types.
However what I don't like - is that index.ts contains not only types but also grpc-relevant resolvers.
So in my case those additional lines are not really needed. So having an opportunity to have separately types.d.ts along with index.ts would entirely solve my issue?
Do you think is possible now?
Is it difficult to adjust
mesh build
command to support this feature?Thank you!
The text was updated successfully, but these errors were encountered: