-
-
Notifications
You must be signed in to change notification settings - Fork 68
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
Removed redundant hasImage
prop from CallToActionNode
#1455
Conversation
hasImage
prop from CTA NodehasImage
prop from CallToActionNode
Caution Review failedThe pull request is closed. WalkthroughThis pull request removes the Possibly related PRs
Suggested reviewers
Warning There were issues while running some tools. Please review the errors and either fix the tool’s configuration or disable the tool if it’s a critical failure. 🔧 ESLint
yarn install v1.22.22 📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (4)
✨ 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 (
|
no issue
The
hasImage
property was unnecessary as the presence of an image can be reliably determined by checking if imageUrl is set. This prop was originally carried over from the signup node, which has an explicit image toggle, but serves no purpose in theCallToActionNode
since there's no other mechanism to enable/disable image usage.hasImage
from the node definition and defaultsimageUrl
directly instead of hasImagehasImage
related test assertions