Skip to content

MR-34: Block protection styling needs a margin fix#20

Open
av3nger wants to merge 1 commit into
mainfrom
fix/MR-34-block-protection
Open

MR-34: Block protection styling needs a margin fix#20
av3nger wants to merge 1 commit into
mainfrom
fix/MR-34-block-protection

Conversation

@av3nger

@av3nger av3nger commented Jun 22, 2026

Copy link
Copy Markdown
Collaborator

Summary

Adds spacing between the "Please select at least one plan." warning and the "Hide when the above conditions are met" toggle in the Memberful Visibility block inspector, so the toggle no longer sits flush against the red error notice.

What's included

  • Wrap the plan-selection error Notice in a @wordpress/components Spacer.
  • Applied to the notice (which only renders when no plan is selected), so the logged-in and plans-selected states keep their existing toggle spacing.

Test plan

  • In the block editor, select a block → Memberful Visibility → "Specific membership plan" with no plans checked; confirm a clear gap between the red notice and the "Hide when the above conditions are met" toggle.
  • Switch to "All logged-in members", and to "Specific membership plan" with a plan checked; confirm the toggle spacing is unchanged (no extra gap).

@coderabbitai

coderabbitai Bot commented Jun 22, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@av3nger, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 7 minutes and 37 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository: TheCodeCompany/coderabbit/.coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: f3f0fc6c-b666-4b28-9008-ef9cf13be12b

📥 Commits

Reviewing files that changed from the base of the PR and between 26e44f1 and 190fb4e.

📒 Files selected for processing (1)
  • wordpress/wp-content/plugins/memberful-wp/js/src/blocks/extensions/block-visibility/index.js
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/MR-34-block-protection

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants