-
Notifications
You must be signed in to change notification settings - Fork 0
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
[Lexical][UI Gallery] Fix meta lexical website intern build errors #35
base: main
Are you sure you want to change the base?
[Lexical][UI Gallery] Fix meta lexical website intern build errors #35
Conversation
…ages and apis related autogenerated docs
Clone of the PR facebook/lexical#6300 |
My review is in progress 📖 - I will have feedback for you in a few minutes! |
Warning Rate limit exceeded@furwellness has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 28 minutes and 23 seconds before requesting another review. How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have reviewed your code and found 1 potential issue.
process.env.FB_INTERNAL | ||
? { | ||
href: 'https://lexical.dev/docs/packages/lexical', | ||
label: 'Packages', | ||
type: 'link', | ||
} | ||
: { | ||
items: [ | ||
{ | ||
dirName: 'packages', | ||
type: 'autogenerated', | ||
}, | ||
], | ||
label: 'Packages', | ||
type: 'category', | ||
}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The conditional rendering based on process.env.FB_INTERNAL
is a good approach for differentiating between internal and external builds. However, it's important to ensure that this environment variable is always defined to avoid potential runtime errors. Consider adding a default value or error handling for cases where FB_INTERNAL
might be undefined. For example, you could use a default value like this: process.env.FB_INTERNAL === 'true'
to ensure it's always a boolean value.
Chat with Korbit by mentioning @korbit-ai, and give a 👍 or 👎 to help Korbit improve your reviews.
/review |
PR Reviewer Guide 🔍(Review updated until commit f68d1f6)
|
Persistent review updated to latest commit f68d1f6 |
@coderabbitai review |
Actions performedReview triggered.
|
@coderabbitai full review |
Actions performedFull review triggered. |
No comment from coderabbit |
WHAT
Fix meta lexical website intern build errors
WHY
TEST
tested locally, everything works as is for Extern Lexical Website
Description by Korbit AI
Note
This feature is in early access. You can enable or disable it in the Korbit Console.
What change is being made?
Conditionally load internal packages and plugins based on the
FB_INTERNAL
environment variable to fix build errors on the meta lexical website.Why are these changes being made?
The build errors occur due to the inclusion of internal packages and plugins that are not available in the public build environment. This change ensures that these internal dependencies are only loaded when the
FB_INTERNAL
environment variable is set, preventing build failures in public environments.