Fix: Error: A type naming conflict has occurred #43
Open
msand wants to merge 1 commit intomlipscombe:masterfrom
Open
Fix: Error: A type naming conflict has occurred #43msand wants to merge 1 commit intomlipscombe:masterfrom
msand wants to merge 1 commit intomlipscombe:masterfrom
Conversation
…ried to define the same type
|
Bumped into the same error on a project, this fix solves it. (apologies if this is not the appropriate plate to comment). |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Error: A type naming conflict has occurred - two entities have tried to define the same type 'SomeEntityInput'.…
Any improvement suggestions to this? This certainly makes for very long type names. Doesn't matter too much though.