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
Hello! I was trying to make type inheritance work in graphql and your library is perfect for this. There is just one small issue that doesn't let me use it out of the box: when I call transpileSchema - it runs some checks, for example this one: https://github.com/nicolasdao/graphql-s2s/blob/master/src/graphqls2s.js#L894. And it breaks in case of schema stiching.
In my pipeline I use .graphql files and I made a very simple loader:
this runs before graphql-tag loader and it works just fine if I comment out those interface checks.
Would be nice if there was a flag that could ignore those checks if it's passed. I can probably contribute, but would be nice if you could point what other places should be affected by that flag.
The text was updated successfully, but these errors were encountered:
healqq
changed the title
Feature request: add a flag to transpileSchema to skip schema cheks
Feature request: add a flag to transpileSchema to skip schema checks
Oct 17, 2019
// index.js
import { transpileSchema } from 'graphql-s2s';
const type = `
type Entity implements Identifiable {
id: Int!
}
`;
// Should not throw an exception that Identifiable is not defined
const schema = transpileSchema(type);
Hello! I was trying to make type inheritance work in graphql and your library is perfect for this. There is just one small issue that doesn't let me use it out of the box: when I call
transpileSchema
- it runs some checks, for example this one: https://github.com/nicolasdao/graphql-s2s/blob/master/src/graphqls2s.js#L894. And it breaks in case of schema stiching.In my pipeline I use .graphql files and I made a very simple loader:
this runs before graphql-tag loader and it works just fine if I comment out those interface checks.
Would be nice if there was a flag that could ignore those checks if it's passed. I can probably contribute, but would be nice if you could point what other places should be affected by that flag.
The text was updated successfully, but these errors were encountered: