Adds docs about removing any UserCredential relationship manually from generated User SDL #6672
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.
In response to this Issue: #5841, specifically the comments that start here: #5841 (comment)
These users were generating a
User
SDL after making theUserCredential
schema changes. The SDL/scaffold generator would add aUserCredential
type to theUser
SDL, assuming that you wanted to access those child records. Since there was no requisiteUserCredential
SDL file, that type was undefined, which makes the api server blow up:We plan on adding this field name to our upcoming allow/blocklist of generated fields (along with stuff like
hashedPassword
andsalt
) so that it doesn't not get generated by default and confuse folks who suddenly start getting errors.