Skip to content

Default non-defined graphql operations to have 0 complexity #89

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Merged

Conversation

BasKiers
Copy link
Contributor

This fixes the TypeError: Cannot read properties of undefined (reading 'name') reported by #84 and #85.

Defaulting to 0 complexity seems reasonable as we cannot reason about fields for which we do not have a type definition.

@BasKiers BasKiers force-pushed the fix/ignore-non-defined-graphql-operations branch 2 times, most recently from 4b959b3 to 4be85d8 Compare September 19, 2023 13:34
@ivome ivome merged commit 9cadc5a into slicknode:master May 28, 2024
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants