We currently strip them, what's the use case?

I was having troubles with the introspection until I removed or increased the complexity limit, so I was assuming it was applying there as well. I'd prefer not to have the complexity limit apply to introspection.

If you already do that, perhaps there's some change I've made that's impacting here?

I am having a similar problem, when I set a complexity limit, and reload my graphiql page, I get this error:

{
  "errors": [
    {
       "message": "operation has complexity 179, which exceeds the limit of 5"
    }
  ],
  "data": null
}

and the documentation panel in graphiql won't show my schema.

I looked in generated.go if I could find something that I could use to exclude the schema introspection from the complexity limitation, but didn't find anything.

When I remove or increase the complexity limit to >179, the above error goes away and graphiql display my schema in the documentation panel again.

interesting. I get the same issue except I get a constant 422 response from the server. Increasing the value like rakete suggested solved the problem

+1, set up the query complexity, but I still want to the user can fetch the schema with low complexity value.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

I am still interested in this, so would like the issue to be kept open if that's ok.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

Still interested

I've solved the problem using a directive that makes the walker skip part of the tree.
https://github.com/jensneuse/graphql-go-tools/blob/db8e785954af348f8c594a819162b60e0b0f6ab7/pkg/middleware/operation_complexity/operation_complexity_test.go#L229