Enrique da Costa Cambio
Enrique da Costa Cambio
One of the other zanzibar-like implementations seems to be addressing this by taking in "contextual tuples" in the "check permission" endpoint, which means the check behaves as if those relationships...
This causes apollo-federated schemas to fail because `_FieldSet` is only used in directives. ``` Caused by: graphql.kickstart.tools.SchemaError: Expected type '_FieldSet' to be a GraphQLInputType, but it wasn't! Was a type...
this can be reproduced with: ```java package test; import java.util.stream.Collectors; import java.util.stream.Stream; import org.junit.Test; import graphql.GraphQL; import graphql.kickstart.tools.GraphQLQueryResolver; import graphql.kickstart.tools.SchemaParser; import graphql.kickstart.tools.SchemaParserBuilder; import graphql.scalar.GraphqlStringCoercing; import graphql.schema.DataFetchingEnvironment; import graphql.schema.GraphQLScalarType; import graphql.schema.GraphQLSchema;...
@oryan-block is this easy to fix? i never coded in kotlin but if you give me a few pointers I can give it a shot.
Maybe your set up is different, but while you source schema might lack a `Query` type, the federation-ready schema will always define one because of `_entities` and `_service`. Perhaps you...
i wanted to share a couple of thoughts on this ### Topic 1: Determining the type of an exported variable I think it is better to statically determine type of...
are there any plans for this?
I agree with @edorivai, this proposal could really take inspiration from GraphGL Federation. It is a nice way to have separation of concerns for different microservices.
i think what is lacking is that when using a type from another file you should re-declare the relations that you are just "importing to be used" but not adding...
@josephschorr I was actually proposing the opposite; that you duplicate everything you want to use the other file: File 1: ``` definition user {} definition organization { relation admin: user...