Update version to 0.1.1

[Amanmahe]

@lorforlinux,

This PR updates the version of the Chords LSL Connector App from 0.1.1 to 0.1.2.

Please review and merge. 🚀

Summary by CodeRabbit

• Chores
  • Application version updated to 0.1.2.
• Refactor
  • Internal improvements to error handling and component management were made, ensuring that the 404 page and general error presentation remain consistent for users.

[coderabbitai]

Walkthrough

The pull request updates internal identifiers across several output files that affect state management and component references. In the 404 page, index HTML, and index TXT, the "b" field value is changed and, in index TXT, a nested component identifier is updated. The overall structure and error handling remain unchanged. Additionally, the application version is bumped from 0.1.1 to 0.1.2 in both package.json and the Cargo.toml file.

Changes

File(s)	Change Summary
out/404.html, out/index.html, out/index.txt	Updated internal state identifiers in JavaScript/JSON structures (e.g., "b" field changed from "WWnxY5-hbokyI2J_rrflq" to "iGz7qAmrpruNs7-Lu4cUc"); index.txt also updates a nested component ID.
package.json, src-tauri/Cargo.toml	Application version updated from "0.1.1" to "0.1.2".

Poem

I'm a rabbit with code in my hop,
Updating IDs so nothing will stop.
New version vibes in JSON and script,
Every change neatly, perfectly equipped.
Hopping along with version new,
Celebrating fixes in every view!

Tip

🌐 Web search-backed reviews and chat

• We have enabled web search-based reviews and chat for all users. This feature allows CodeRabbit to access the latest documentation and information on the web.
• You can disable this feature by setting web_search: false in the knowledge_base settings.
• Please share any feedback in the Discord discussion.

---

📜 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 2774371 and 97166ee.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (5)

• out/404.html (1 hunks)
• out/index.html (1 hunks)
• out/index.txt (1 hunks)
• package.json (1 hunks)
• src-tauri/Cargo.toml (1 hunks)

✅ Files skipped from review due to trivial changes (2)

• src-tauri/Cargo.toml
• package.json

🔇 Additional comments (3)

out/index.txt (1)

13-13: Validate Updated Identifier in JSON Configuration
The "b" field has been updated to "iGz7qAmrpruNs7-Lu4cUc". Please confirm that this change is intentional and that all downstream components or caching mechanisms dependent on this identifier are updated accordingly.

out/index.html (1)

1-1: Confirm Consistency of Application State in Script Payloads
The embedded JSON payload pushed via self.__next_f.push now reflects the new "b" value ("iGz7qAmrpruNs7-Lu4cUc") and updated component identifiers (e.g. "JbVG6hA6ezvH8fnS8JuD_"). Please verify that these changes align with the intended build and state management configuration and that no client-side inconsistencies occur.

out/404.html (1)

1-1: Ensure Identifier Consistency on Error Page
Similar to other output files, the "b" field here is updated to "iGz7qAmrpruNs7-Lu4cUc". Confirm that this update is applied intentionally and that the error page’s state management remains coherent with the rest of the application.

---

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.