Add persist feature to BitTheme (#9707)

[msynk]

closes #9707

Summary by CodeRabbit

• New Features

  • Enabled theme persistence across user sessions, so users’ selected themes now remain active after revisiting.

• Style

  • Improved code formatting for enhanced readability.

[coderabbitai]

Important

Review skipped

Auto incremental reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

The changes introduce theme persistence within the BitTheme class by adding a static property to store the local storage key. The initialization method now checks an options flag (persist) to retrieve the saved theme from local storage, and the method to change themes updates local storage accordingly. Additionally, the demo client configuration is updated to enable persistence and includes minor formatting improvements for readability.

Changes

File(s)	Change Summary
.../Bit.BlazorUI/Utils/Theme/bit-theme.ts	Added a static property (THEME_SOTRAGE_KEY) to hold the theme storage key. Modified init to load the theme from local storage when options.persist is true and updated set to store the theme.
.../Bit.BlazorUI.Demo.Client.Core/Scripts/app.ts	Introduced a new persist: true option in the BitTheme initialization and applied minor formatting adjustments in setAttribute calls.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant BitTheme
    participant localStorage

    User->>BitTheme: Initialize theme (persist: true)
    BitTheme->>localStorage: getItem(THEME_SOTRAGE_KEY)
    localStorage-->>BitTheme: Return stored theme value (if any)
    User->>BitTheme: Request theme change
    BitTheme->>localStorage: setItem(THEME_SOTRAGE_KEY, newTheme)

Loading

Poem

Oh, I’m a bunny, hopping in the code,
Making themes persist on every node.
A key is set and themes abide,
In local storage, they safely reside.
A joyful hop to improvements so bright 🐇✨!

---

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. (Beta)
• @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.

[coderabbitai]

Actionable comments posted: 4

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between cc729eb and 22f3850.

📒 Files selected for processing (2)

• src/BlazorUI/Bit.BlazorUI/Utils/Theme/bit-theme.ts (3 hunks)
• src/BlazorUI/Demo/Client/Bit.BlazorUI.Demo.Client.Core/Scripts/app.ts (1 hunks)

🧰 Additional context used

🪛 Biome (1.9.4)

src/BlazorUI/Bit.BlazorUI/Utils/Theme/bit-theme.ts

[error] 18-18: Using this in a static context can be confusing.

this refers to the class.
Unsafe fix: Use the class name instead.

(lint/complexity/noThisInStatic)

---

[error] 18-18: Using this in a static context can be confusing.

this refers to the class.
Unsafe fix: Use the class name instead.

(lint/complexity/noThisInStatic)

---

[error] 18-18: Using this in a static context can be confusing.

this refers to the class.
Unsafe fix: Use the class name instead.

(lint/complexity/noThisInStatic)

---

[error] 43-43: Using this in a static context can be confusing.

this refers to the class.
Unsafe fix: Use the class name instead.

(lint/complexity/noThisInStatic)

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

• GitHub Check: build and test

🔇 Additional comments (2)

src/BlazorUI/Demo/Client/Bit.BlazorUI.Demo.Client.Core/Scripts/app.ts (2)

36-36: LGTM! Theme persistence enabled.

The persist: true option enables theme persistence across sessions, enhancing user experience.

---

41-41: LGTM! Consistent formatting.

The formatting change maintains consistency with similar code at line 45.