-
Notifications
You must be signed in to change notification settings - Fork 199
refactor!: mark isNullish and isNotNullish as private
#661
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
BREAKING CHANGES: the `utils.isNullish` and `utils.isNotNullish` functions are now marked as private. They had been made public by mistake, and had been considered internal since their introduction.
|
Caution Review failedThe pull request is closed. WalkthroughThe update revises documentation and utility modules. In the changelog, a new "Breaking Changes" section under "Unreleased" has been added to note that the functions Changes
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (2)
✨ Finishing Touches
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 using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
# Conflicts: # CHANGELOG.md
|



BREAKING CHANGES: the
utils.isNullishandutils.isNotNullishfunctions are now marked as private.They had been made public by mistake, and had been considered internal since their introduction.
Summary by CodeRabbit
Documentation
Chores