Ashi Krishnan
Ashi Krishnan
could we consider allowing d-o-ds to apply to individual locations? a use case is when a directive is `@deprecated` in one location, but not in another: ```graphql directive @explode(arg: Type)...
bad news: we're likely removing `printSubgraphSchema` in #1554 good news: this is fixed in #1554 unsettling news: we have tests for this, so i don't know why it isn't working....
it's also fine to use `@private`, imo—`@tag` is really a placeholder for users eventually being able to do contracts assertions on whatever custom directives they want
Currently, yes, the recommended strategy is to alter the downstream schema which, yes, is not the best answer if you don't control it. We're looking at various ways to support...
it seems like it would make sense to just remove `printSubgraphSchema` and direct users to this as a replacement? as of #1554, we are no longer using `printSubgraphSchema` in subgraph-js,...
Ahhhh. Okay, that's fair. I'll tweak this PR to do that.
@feffy380 were you able to work around this while using guidance?