fix(css-map): replace lyrics-lyricsContent-active key

[Kamiloo13]

Previous changes introduced in this pr; added new keys for lyrics and one of them (lyrics-lyricsContent-active) is wrong and should be changed to _gZrl2ExJwyxPy1pEUG2. The F8gozO67UMCQqFoPmjyn key is present on all lyrics containers while it should only be visible on one.

I'm not entirely sure for what this key (F8gozO67UMCQqFoPmjyn) was responsible in the previous version though. Right now it has only one line in css: margin-bottom: .6em;

Summary by CodeRabbit

• Chores
  • Updated an internal CSS mapping identifier to ensure consistency and maintainability. This change does not affect styling behavior or functionality.
  • No user-facing changes; the app’s appearance and interactions remain the same.
  • Improves long-term reliability of style references without altering performance, layout, or accessibility.

[coderabbitai]

Walkthrough

Rekeyed a single entry in css-map.json: removed key "F8gozO67UMCQqFoPmjyn" mapped to "lyrics-lyricsContent-active" and added key "_gZrl2ExJwyxPy1pEUG2" with the same value. No other mappings or logic changed.

Changes

Cohort / File(s)	Summary
CSS map rekey css-map.json	Replaced hashed key "F8gozO67UMCQqFoPmjyn" with "_gZrl2ExJwyxPy1pEUG2" for value "lyrics-lyricsContent-active"; no additional modifications.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• feat(css-map): update css-map for 1.2.72 #3511 — Similar css-map.json rekeying of hashed IDs to existing CSS class names.
• feat(css-map): add missing lyrics classes #3524 — Touches the same "lyrics-lyricsContent-active" mapping; previously added the removed key.

Suggested reviewers

• rxri

Poem

A hop, a swap, a tiny key,
I twitch my nose—consistency!
Old hash out, new hash in,
The lyrics glow; same silky skin.
Thump-thump—map’s aligned just right,
Carrot-coded, crisp and light. 🥕✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The title accurately summarizes the main change by indicating that the css-map key for lyrics-lyricsContent-active is being replaced and uses a clear conventional commit style prefix. It is concise, focused on the key alteration, and does not include unrelated details. A teammate scanning the history can understand the primary update from the title alone.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 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 b7addd9 and 721c529.

📒 Files selected for processing (1)

• css-map.json (1 hunks)

🔇 Additional comments (1)

css-map.json (1)

158-158: Mapping correction looks good.

Thanks for swapping in _gZrl2ExJwyxPy1pEUG2; this should realign lyrics-lyricsContent-active with the single container that still uses that hash in the latest build. No further issues spotted in this segment.

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

• Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
• Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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