docs(plugin-form-builder): add warning about GraphQL type name collis… #12720
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ions and resolution steps
paulpopus
requested changes
Jun 8, 2025
- Replaced warning with an info banner - Moved GraphQL type name collision info into its own dedicated section
…hQL naming conflicts
paulpopus
approved these changes
Jun 8, 2025
|
🚀 This is included in version v3.42.0 |
elliott-w
pushed a commit
to elliott-w/payload
that referenced
this pull request
Jun 12, 2025
payloadcms#12720) ### What? Add a warning to the form builder plugin docs about potential GraphQL type name collisions with custom Blocks or Collections. ### Why? To help users avoid schema errors caused by conflicting type names and guide them with resolution options.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What?
Add a warning to the form builder plugin docs about potential GraphQL type name collisions with custom Blocks or Collections.
Why?
To help users avoid schema errors caused by conflicting type names and guide them with resolution options.