chore: update deps

[Enubia]

No description provided.

[coderabbitai]

Walkthrough

The recent modifications streamline the codebase by enhancing type safety and clarity. Key changes involve removing an experimental ESLint feature, refining TypeScript types with enumerations for constants, and refactoring function signatures to accept parameters directly. These updates improve maintainability, reduce error likelihood, and align with best practices in TypeScript and Vue.js, ultimately fostering a more robust and modular application structure.

Changes

Files	Change Summary
.vscode/settings.json	Removed ESLint's flat config support; simplified settings to disable default formatter and format on save.
shared/constants/store.ts	Updated import statements to include FontSize and Stroke; changed properties in StoreDefaults to use enumerated types.
shared/types/store.ts	Introduced FontSize and Stroke enums to enhance type definitions; updated Kick interface to reflect new types.
src/pages/settings/kick.vue	Refactored async function signatures to accept parameters; updated event handler for fade timeout input for better reactivity.

Poem

🐇 In the garden of code, we've made a change,
With enums to keep things tidy and strange.
Functions now dance with parameters bright,
Making our settings more clear, just right!
Hopping along, we embrace the new day,
In the world of TypeScript, we joyfully play! 🌼

---

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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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 as 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 resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

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: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between af1be63 and bac4519.

Files ignored due to path filters (2)

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

Files selected for processing (4)

• .vscode/settings.json (1 hunks)
• shared/constants/store.ts (2 hunks)
• shared/types/store.ts (1 hunks)
• src/pages/settings/kick.vue (4 hunks)

Files skipped from review due to trivial changes (1)

• .vscode/settings.json

Additional comments not posted (15)

shared/constants/store.ts (2)

1-1: Improved Type Safety with Enumerated Types.

The import statement now includes FontSize and Stroke types, enhancing type safety by using enums instead of string literals. This change aligns with TypeScript best practices.

---

38-39: Use of Enumerated Types for fontSize and stroke.

The properties fontSize and stroke in StoreDefaults now use the FontSize and Stroke enums. This change reduces errors associated with string literals and improves code maintainability.

shared/types/store.ts (3)

27-31: Introduction of FontSize Enum.

The FontSize enum provides a clear and type-safe way to handle font size options, reducing the risk of errors from using string literals.

---

33-39: Introduction of Stroke Enum.

The Stroke enum enhances type safety by providing predefined options for stroke values, which helps prevent errors due to typos in string literals.

---

42-43: Updated Kick Interface with Enums.

The Kick interface now uses FontSize and Stroke enums for fontSize and stroke properties. This change improves type safety and aligns with the updated type definitions.

src/pages/settings/kick.vue (10)

14-14: Type Imports for Improved Type Safety.

Importing FontSize and Stroke types enhances type safety in the file, ensuring that the correct types are used for related properties.

---

47-49: Refactored saveDefaultChannel Function.

The function now accepts a value parameter, improving clarity and making the function more reusable and easier to test.

---

53-54: Refactored saveFontSize Function.

The function now takes a value parameter and casts it to FontSize, improving type safety and flexibility.

---

57-58: Refactored saveStroke Function.

The function now accepts a value parameter and casts it to Stroke, enhancing type safety and modularity.

---

61-62: Refactored saveAnimate Function.

The function now takes a value parameter of type boolean, improving modularity and reusability.

---

65-66: Refactored saveFadeMessages Function.

The function now accepts a value parameter of type boolean, enhancing clarity and flexibility.

---

69-70: Refactored saveBadges Function.

The function now takes a value parameter of type boolean, improving modularity and reusability.

---

73-74: Refactored saveCommands Function.

The function now accepts a value parameter of type boolean, enhancing clarity and flexibility.

---

77-78: Refactored saveBots Function.

The function now takes a value parameter of type boolean, improving modularity and reusability.

---

91-94: Refactored saveFadeTimeout Function.

The function now accepts a value parameter of type string | number, enhancing flexibility. Ensure that Number.parseInt is used correctly to handle potential string inputs.