Skip to content

fix(compat): allow v-model built in modifiers on component #12654

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

markrian
Copy link
Contributor

@markrian markrian commented Jan 6, 2025

close #12652
This is a rough attempt at fixing #12652.

Summary by CodeRabbit

  • Bug Fixes

    • Improved handling of v-model modifiers (such as .trim) for custom input components, ensuring correct behavior and compatibility.
  • Tests

    • Added new tests to verify that v-model modifiers work as expected with custom input components and trigger appropriate deprecation warnings.

Copy link

github-actions bot commented Jan 7, 2025

Size Report

Bundles

File Size Gzip Brotli
runtime-dom.global.prod.js 101 kB 38.4 kB 34.6 kB
vue.global.prod.js 159 kB 58.5 kB 52.2 kB

Usages

Name Size Gzip Brotli
createApp (CAPI only) 46.7 kB 18.2 kB 16.7 kB
createApp 54.6 kB 21.3 kB 19.4 kB
createSSRApp 58.9 kB 23 kB 21 kB
defineCustomElement 59.6 kB 22.9 kB 20.9 kB
overall 68.7 kB 26.4 kB 24.1 kB

Copy link

pkg-pr-new bot commented Jan 7, 2025

Open in StackBlitz

@vue/compiler-core

npm i https://pkg.pr.new/@vue/compiler-core@12654

@vue/compiler-dom

npm i https://pkg.pr.new/@vue/compiler-dom@12654

@vue/compiler-sfc

npm i https://pkg.pr.new/@vue/compiler-sfc@12654

@vue/compiler-ssr

npm i https://pkg.pr.new/@vue/compiler-ssr@12654

@vue/reactivity

npm i https://pkg.pr.new/@vue/reactivity@12654

@vue/runtime-core

npm i https://pkg.pr.new/@vue/runtime-core@12654

@vue/runtime-dom

npm i https://pkg.pr.new/@vue/runtime-dom@12654

@vue/server-renderer

npm i https://pkg.pr.new/@vue/server-renderer@12654

@vue/shared

npm i https://pkg.pr.new/@vue/shared@12654

vue

npm i https://pkg.pr.new/vue@12654

@vue/compat

npm i https://pkg.pr.new/@vue/compat@12654

commit: 0dbd87d

`compatModelEventPrefix + event in props` can only be true if
`isCompatEnabled(DeprecationTypes.COMPONENT_V_MODEL, instance)`; see
`convertLegacyVModelProps`.
@edison1105 edison1105 added ready to merge The PR is ready to be merged. scope: v2 compat 🔨 p3-minor-bug Priority 3: this fixes a bug, but is an edge case that only affects very specific usage. and removed wait changes labels Jan 7, 2025
@edison1105
Copy link
Member

edison1105 commented Jan 7, 2025

@markrian
LGTM~ Thank you for resolving the issue you raised.

@miguelrincon
Copy link

@edison1105 pinging you because it looks like this could be merged. Thanks!

Copy link

coderabbitai bot commented Jun 11, 2025

Walkthrough

The changes update the handling of v-model modifiers for Vue components under the @vue/compat build. Logic is added to check and apply model modifiers on component events prefixed with a compatibility model event. New tests verify that v-model modifiers such as .trim work correctly in compat mode, including with custom model options.

Changes

File(s) Change Summary
packages/runtime-core/src/componentEmits.ts Enhanced event handling to detect compat model listeners and apply model modifiers accordingly under the __COMPAT__ flag.
packages/vue-compat/tests/componentVModel.spec.ts Added helper and new tests to verify v-model modifiers (e.g., .trim) work on components in compat mode, including custom model opts.

Sequence Diagram(s)

sequenceDiagram
    participant ParentComponent
    participant CustomInput
    participant VueCompatRuntime

    ParentComponent->>CustomInput: v-model.trim="text"
    CustomInput-->>ParentComponent: Emits compat model event (e.g., 'compat:modelValue')
    VueCompatRuntime->>CustomInput: Detects compat model event
    VueCompatRuntime->>VueCompatRuntime: Applies .trim modifier if present
    VueCompatRuntime-->>ParentComponent: Updates 'text' with trimmed value
Loading

Assessment against linked issues

Objective Addressed Explanation
v-model modifiers should work when used on components under @vue/compat (#12652)

Assessment against linked issues: Out-of-scope changes

No out-of-scope changes found.

Poem

A bunny hopped through Vue's old code,
Bringing v-model modifiers down the compat road.
With .trim and friends, the inputs now gleam,
Old and new, they work as a team!
Tests now cheer, and warnings chime,
All thanks to a fix that's simply sublime! 🐰✨

✨ Finishing Touches
  • 📝 Generate Docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 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.
    • Explain this complex logic.
    • 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 explain this code block.
    • @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 explain its main purpose.
    • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this 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.

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.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (3)
packages/runtime-core/src/componentEmits.ts (2)

154-156: Add parentheses to avoid precedence ambiguity

The concatenation (+), in, and && operators have different precedences.
Although the current expression happens to evaluate correctly, the lack of
parentheses forces the reader to recall those rules and makes the code easy to
mis-read on a quick scan.

-const isCompatModelListener =
-  __COMPAT__ && compatModelEventPrefix + event in props
+const isCompatModelListener =
+  __COMPAT__ &&
+  (compatModelEventPrefix + event) in props

157-159: Minor: extract helper for modifiers lookup

isCompatModelListener ? props.modelModifiers : getModelModifiers(...)
is duplicated (or very similar) in several places in the code-base. A tiny
utility such as resolveModelModifiers(props, event, isCompat) would make this
branching logic self-documenting and cut 6–7 bytes from the non-compat build
after minification.

Not blocking, just something to consider.

packages/vue-compat/__tests__/componentVModel.spec.ts (1)

110-114: Avoid the banned Function type

Function is deliberately broad and flagged by Biome/TSLint/ESLint because it
silently accepts anything callable. Cast to the actual shape you need:

-  (deprecationData[DeprecationTypes.COMPONENT_V_MODEL].message as Function)(
+  (
+    deprecationData[DeprecationTypes.COMPONENT_V_MODEL]
+      .message as (c: ComponentOptions) => string
+  )(

This tightens the type-check and removes the linter warning.

🧰 Tools
🪛 Biome (1.9.4)

[error] 111-111: Don't use 'Function' as a type.

Prefer explicitly define the function shape. This type accepts any function-like value, which can be a common source of bugs.

(lint/complexity/noBannedTypes)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between e8e8422 and d11784f.

📒 Files selected for processing (2)
  • packages/runtime-core/src/componentEmits.ts (1 hunks)
  • packages/vue-compat/__tests__/componentVModel.spec.ts (1 hunks)
🧰 Additional context used
🧬 Code Graph Analysis (2)
packages/runtime-core/src/componentEmits.ts (2)
packages/runtime-core/src/compat/componentVModel.ts (1)
  • compatModelEventPrefix (12-12)
packages/runtime-core/src/helpers/useModel.ts (1)
  • getModelModifiers (120-129)
packages/vue-compat/__tests__/componentVModel.spec.ts (1)
packages/runtime-core/src/compat/compatConfig.ts (1)
  • deprecationData (74-426)
🪛 Biome (1.9.4)
packages/vue-compat/__tests__/componentVModel.spec.ts

[error] 111-111: Don't use 'Function' as a type.

Prefer explicitly define the function shape. This type accepts any function-like value, which can be a common source of bugs.

(lint/complexity/noBannedTypes)

🔇 Additional comments (1)
packages/vue-compat/__tests__/componentVModel.spec.ts (1)

116-122: Nice coverage of .trim behaviour

The assertions correctly validate both the model update and the reflected input
value after the modifier is applied. Good job extending the test matrix to
cover custom model options as well.

@edison1105 edison1105 merged commit cb14b86 into vuejs:main Jun 18, 2025
18 of 19 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🔨 p3-minor-bug Priority 3: this fixes a bug, but is an edge case that only affects very specific usage. ready to merge The PR is ready to be merged. scope: v2 compat
Projects
None yet
Development

Successfully merging this pull request may close these issues.

compat: v-model modifiers do not work on components
4 participants