-
Notifications
You must be signed in to change notification settings - Fork 620
[Dashboard] Fix: Handle null publisher profile #5372
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
Conversation
|
Your org has enabled the Graphite merge queue for merging into mainAdd the label “merge-queue” to the PR and Graphite will automatically add it to the merge queue when it’s ready to merge. Or use the label “hotfix” to add to the merge queue as a hot fix. You must have a Graphite account and log in to Graphite in order to use the merge queue. Sign up using this link. |
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
This stack of pull requests is managed by Graphite. Learn more about stacking. |
0444a72 to
38d6e8c
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #5372 +/- ##
=======================================
Coverage 45.52% 45.52%
=======================================
Files 1070 1070
Lines 55665 55665
Branches 4030 4030
=======================================
Hits 25341 25341
Misses 29637 29637
Partials 687 687
*This pull request uses carry forward flags. Click here to find out more. |
size-limit report 📦
|
Merge activity
|
38d6e8c to
b30c4d0
Compare

PR-Codex overview
This PR focuses on handling the case where
publisherProfilecan benull, ensuring that the UI components render correctly without errors whenpublisherProfileis not available.Detailed summary
publisherProfiletype fromProfileMetadatatoProfileMetadata | null.?.) to safely accessbioproperty.PublisherSocialsandEditProfilecomponents with conditional rendering to check forpublisherProfile.