chore(#117): add value watch model set

[Decipher]

Types of changes

• Bug fix (a non-breaking change which fixes an issue)
• New feature (a non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Description

Checklist:

• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my changes (if not applicable, please state why)
• All new and existing tests are passing.

Screenshots/Media:

Summary by CodeRabbit

New Features:

• Enhanced the Checkbox component in our application. It now updates and synchronizes its state more effectively, providing a smoother user experience.
• The component will now emit an 'input' event when its state changes, allowing other parts of the application to react to these changes more efficiently.

[coderabbitai]

Walkthrough

The recent changes in the codebase primarily focus on enhancing the synchronization between the model and value props in the Vue component. The modifications also ensure that an input event is emitted whenever the model changes, thereby improving the component's reactivity and data flow.

Changes

File Path	Summary
src/.../Checkbox.vue	A watch block for value prop is added to update the model data property. In the model watcher, an input event is emitted when model changes.

Poem

"In the heart of fall, under the chestnut tree, 🍂🌰
Code changes dance, as lively as can be. 💃🕺
Syncing props and models, in a Vue component spree,
Emitting events, like whispers of the sea. 🌊
Celebrate the changes, for they're as sweet as tea, 🍵
In the world of code, they bring harmony. 🎶🐇"

---

Tips

Chat with CodeRabbit Bot (@coderabbitai)

• If you reply to a review comment from CodeRabbit, the bot will automatically respond.
• To engage with CodeRabbit bot directly around the specific lines of code in the PR, mention @coderabbitai in your review comment
• Note: Review comments are made on code diffs or files, not on the PR overview.
• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

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 a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai help to get help.
• @coderabbitai resolve to resolve all the CodeRabbit review comments.

Note: For conversation with the bot, please use the review comments on code diffs or files.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• 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/coderabbit-overrides.json

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between 9fdfed0 and 089e865.

Files selected for processing (1)

• src/components/Checkbox.vue (1 hunks)

Additional comments: 1

src/components/Checkbox.vue (1)

• 62-70: The watch block is correctly implemented to watch for changes in model and value. When model changes, it emits an input event with the new value, and when value changes, it updates model with the new value. This ensures synchronization between model and value and allows the component to respond to changes in model. However, it's important to note that watchers can be computationally expensive and can lead to performance issues if not used judiciously. In this case, it seems necessary to use watchers to achieve the desired functionality, but it's something to keep in mind for future development.