fix(providers): add optional chaining to avoid nullish reference errors #4365
Conversation
This file contains 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
|
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/nextauthjs/next-auth/FKTW8BabsCjLiqsvPNJbxqnNVBLC |
|
That's a fundamental solution to the problem. Thank you for letting me know. |
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.
Reasoning 💡
Hello, I encountered an error while using the Kakao provider.
If you don't select your nickname and profile image in Kakao settings, an 'undefined' error occurs because the profile object is not provided.
Please refer to the picture below.
As you can see in line 40 of the code, the profile is an optional property.
So I changed to get a nickname or profile image only if there is a profile object.
Checklist 🧢
- [ ] Documentation- [ ] Tests