Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

Confusing errors when referencing wrong type name in makeExtendSchemaPlugin #2217

Open
p-bakker opened this issue Oct 21, 2024 · 1 comment
Labels

Comments

@p-bakker
Copy link

Summary

If referencing a non-existing type in a makeExtendSchemaPlugin plugin that targets just one entity, this results in a cascade of exceptions on every subsequent entity

Steps to reproduce

See https://discord.com/channels/489127045289476126/1296863704364879902/1297218564876406947

Expected results

Only 1 exception on the affected entities

Actual results

Exceptions on all subsequent entities

Additional context


(https://discord.com/channels/489127045289476126/1296863704364879902/1297218564876406947)

Possible Solution

@benjie
Copy link
Member

benjie commented Oct 21, 2024

(Reminder to self: the issue was referencing Metadata when the type name was Metadatum. Caused extend plugin to blow up the entire Query type, which then went on to blow up mutation payload types.)

@benjie benjie moved this from 🌳 Triage to 🦟 Mayfly in V5.0.0 Oct 21, 2024
@benjie benjie moved this from 🦟 Mayfly to 🐭 Shrew in V5.0.0 Oct 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: 🐭 Shrew
Development

No branches or pull requests

3 participants
@benjie @p-bakker and others