Moved CTA card behind beta flag

[kevinansfield]

ref https://linear.app/ghost/issue/PLG-365

• moves CTA card from behind alpha flag to private beta flag for wider testing

[coderabbitai]

Walkthrough

The changes update the visibility condition logic for the Call To Action node. In the CallToActionNode class, the isHidden function within the kgMenu static property now checks for config?.feature?.contentVisibility instead of config?.feature?.contentVisibilityAlpha. Additionally, the test initialization has been modified: the URI for the initialization function in the test file now includes only the contentVisibility parameter rather than both contentVisibility and contentVisibilityAlpha. The modifications are limited to the internal logic that determines the call-to-action display state, with no changes to any exported or public declarations.

Possibly related PRs

• Updated CTA card icon in card menu #1423: Involves modifications to the CallToActionNode class, specifically updating property logic and conditions similar to the changes in the isHidden function.
• Remove link from toolbar on CTA Card #1450: Modifies the isHidden function while removing the href property from the same class, indicating a direct connection in the handling of the Call To Action node.
• Generalized visibility property logic and added to CallToActionNode #1431: Introduces a hasVisibility property in the CallToActionNode class, which relates directly to the visibility logic adjustments present in the modified isHidden function.

Suggested reviewers

• ronaldlangeveld

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

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

packages/koenig-lexical/src/nodes/CallToActionNode.jsx

Oops! Something went wrong! :(

ESLint: 8.57.0

ESLint couldn't find the config "react-app" to extend from. Please check that the name of the config is correct.

The config "react-app" was referenced from the config file in "/packages/koenig-lexical/.eslintrc.cjs".

If you still have problems, please stop by https://eslint.org/chat/help to chat with the team.

packages/koenig-lexical/test/e2e/cards/call-to-action-card.test.js

Oops! Something went wrong! :(

ESLint: 8.57.0

ESLint couldn't find the config "react-app" to extend from. Please check that the name of the config is correct.

The config "react-app" was referenced from the config file in "/packages/koenig-lexical/.eslintrc.cjs".

If you still have problems, please stop by https://eslint.org/chat/help to chat with the team.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between fcd1708 and 5bb3580.

📒 Files selected for processing (2)

• packages/koenig-lexical/src/nodes/CallToActionNode.jsx (1 hunks)
• packages/koenig-lexical/test/e2e/cards/call-to-action-card.test.js (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (2)

• GitHub Check: Node 22.13.1
• GitHub Check: Node 20.11.1

🔇 Additional comments (2)

packages/koenig-lexical/src/nodes/CallToActionNode.jsx (1)

28-28: Feature flag update aligns with beta release

This change moves the CTA card from an alpha flag (contentVisibilityAlpha) to a more stable beta flag (contentVisibility), which aligns with the PR objective to make this feature available for wider testing.

packages/koenig-lexical/test/e2e/cards/call-to-action-card.test.js (1)

18-18: Updated test initialization to match new feature flag

The test initialization has been properly updated to only include the contentVisibility parameter, matching the change in the implementation. This ensures test consistency with the new feature flag structure.

✨ Finishing Touches

• 📝 Generate Docstrings

---

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?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

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)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.