fix: sync language document attribute

[joshunrau]

Summary by CodeRabbit

• New Features

  • Enhanced translation store with dynamic language management
  • Improved state subscription mechanism for translations

• Chores

  • Updated TypeScript configuration to include Vitest config
  • Migrated test configuration from Vite to dedicated Vitest config file

• Refactor

  • Streamlined test configuration and coverage settings

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The pull request introduces changes to the project's configuration and state management. In the src/i18n/store.ts file, the translation store now uses the subscribeWithSelector middleware, enhancing state subscription capabilities. A new subscription is added to dynamically update the document's language attribute. The tsconfig.json file now includes the vitest.config.mts file. The vite.config.mts file has its test configuration removed, while a new vitest.config.mts file is created with comprehensive test configuration settings.

Changes

File	Change Summary
src/i18n/store.ts	- Added subscribeWithSelector middleware to translation store - Implemented subscription to update document language attribute
tsconfig.json	- Added "vitest.config.mts" to included files
vite.config.mts	- Removed entire test configuration block
vitest.config.mts	- New configuration file for Vitest - Merged with existing Vite config - Defined comprehensive test and coverage settings

Sequence Diagram

sequenceDiagram
    participant Store as Translation Store
    participant Doc as Document
    participant Subscription as Language Subscription

    Store->>Subscription: Subscribe to resolvedLanguage
    Subscription-->>Doc: Update lang attribute
    Doc->>Doc: Change language dynamically

Loading

Poem

🐰 A rabbit's tale of config delight,
Vitest springs with testing might!
Subscriptions dance, languages sway,
Configurations find their way,
Code evolves with bunny's bright sight! 🌟

---

📜 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 f90db70 and a3bd994.

📒 Files selected for processing (4)

• src/i18n/store.ts (3 hunks)
• tsconfig.json (1 hunks)
• vite.config.mts (0 hunks)
• vitest.config.mts (1 hunks)

✨ Finishing Touches

• 📝 Generate Docstrings (Beta)

---

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.

[github-actions]

🎉 This PR is included in version 3.8.7 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀