Skip to content

fix(docs): hide inactive SDK variants for java#386

Merged
pratyush618 merged 1 commit into
masterfrom
fix/docs-java-sdk-variant
Jul 7, 2026
Merged

fix(docs): hide inactive SDK variants for java#386
pratyush618 merged 1 commit into
masterfrom
fix/docs-java-sdk-variant

Conversation

@pratyush618

Copy link
Copy Markdown
Collaborator

Summary

  • The SDK-variant show/hide CSS enumerated only the python/node pairs, so Java variants were never hidden — the architecture overview rendered "Node.jsJava", "N-APIJNI boundary", etc., and with Java active the other SDKs' text also stayed visible
  • Replaced the pairwise enumeration with per-SDK :not() rules covering python, node, and java (adding a future SDK now needs a single selector), and extended the tab-highlight rule to java

Test plan

  • docs lint + typecheck green

The show/hide CSS enumerated python/node pairs only, so with Java
active (or Java variants present) all SDKs rendered concatenated in
the architecture diagram and prose.
@github-actions github-actions Bot added the docs label Jul 7, 2026
@coderabbitai

coderabbitai Bot commented Jul 7, 2026

Copy link
Copy Markdown

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 25 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

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 reviews.

How do review limits work?

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

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, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: baed44ce-6fb1-4aa8-90d5-f7610c2626a6

📥 Commits

Reviewing files that changed from the base of the PR and between 3e15ab6 and ee76583.

📒 Files selected for processing (1)
  • docs/app/styles/sdk.css
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/docs-java-sdk-variant

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

@pratyush618 pratyush618 merged commit 96db9aa into master Jul 7, 2026
14 checks passed
@pratyush618 pratyush618 deleted the fix/docs-java-sdk-variant branch July 7, 2026 10:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant