Skip to content

fix(compiler-core): remove types for expressions #13397

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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

zhiyuanzmj
Copy link
Member

@zhiyuanzmj zhiyuanzmj commented May 28, 2025

similar to #13395

Summary by CodeRabbit

  • Bug Fixes

    • Improved handling of expressions with TypeScript type assertions to ensure correct code generation without extraneous text.
  • Tests

    • Added a new test case to verify proper handling of expressions with type assertions in templates.

Copy link

coderabbitai bot commented May 28, 2025

Walkthrough

A new test case was added to the compiler core's expression transform tests to verify correct handling of TypeScript type assertions in template expressions. Additionally, the transform logic was updated to exclude leading and trailing raw text slices around identifiers when the AST node type is one of the TypeScript node types.

Changes

File(s) Change Summary
packages/compiler-core/tests/transforms/transformExpressions.spec.ts Added a test case to check that expressions with TypeScript type assertions are handled correctly.
packages/compiler-core/src/transforms/transformExpression.ts Modified transform logic to exclude leading/trailing raw text slices around identifiers for TS node types.

Poem

A hop and a skip through code so bright,
TypeScript types now fit just right.
Leading and trailing text take flight,
Leaving expressions clean in sight.
Tests confirm the change is tight,
Rabbits cheer in pure delight! 🐰🎉


📜 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 575fc50 and 6640358.

⛔ Files ignored due to path filters (1)
  • packages/compiler-core/__tests__/transforms/__snapshots__/transformExpressions.spec.ts.snap is excluded by !**/*.snap
📒 Files selected for processing (2)
  • packages/compiler-core/__tests__/transforms/transformExpressions.spec.ts (1 hunks)
  • packages/compiler-core/src/transforms/transformExpression.ts (3 hunks)
🚧 Files skipped from review as they are similar to previous changes (2)
  • packages/compiler-core/src/transforms/transformExpression.ts
  • packages/compiler-core/tests/transforms/transformExpressions.spec.ts
⏰ Context from checks skipped due to timeout of 90000ms (3)
  • GitHub Check: Redirect rules
  • GitHub Check: Header rules
  • GitHub Check: Pages changed
✨ Finishing Touches
  • 📝 Generate Docstrings

🪧 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

Size Report

Bundles

File Size Gzip Brotli
runtime-dom.global.prod.js 101 kB 38.3 kB 34.5 kB
vue.global.prod.js 159 kB 58.5 kB 52 kB

Usages

Name Size Gzip Brotli
createApp (CAPI only) 46.6 kB 18.2 kB 16.7 kB
createApp 54.5 kB 21.2 kB 19.4 kB
createSSRApp 58.8 kB 23 kB 20.9 kB
defineCustomElement 59.5 kB 22.8 kB 20.8 kB
overall 68.6 kB 26.4 kB 24 kB

Copy link

pkg-pr-new bot commented May 28, 2025

Open in StackBlitz

@vue/compiler-core

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

@vue/compiler-dom

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

@vue/compiler-ssr

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

@vue/compiler-sfc

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

@vue/reactivity

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

@vue/runtime-core

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

@vue/runtime-dom

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

@vue/server-renderer

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

@vue/shared

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

vue

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

@vue/compat

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

commit: 6640358

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 (1)
packages/compiler-core/__tests__/transforms/transformExpressions.spec.ts (1)

720-724: Good test coverage for TypeScript type assertions.

The test correctly validates that TypeScript type assertions are preserved in the generated code with proper parentheses wrapping. The assertion checks for the expected output and includes snapshot testing for regression prevention.

Consider adding test cases for other TypeScript node types from TS_NODE_TYPES to ensure comprehensive coverage:

test('expression with various TypeScript types', () => {
  // Test TSNonNullExpression
  const { code: code1 } = compile(`<div @click="value!"></div>`)
  expect(code1).toMatch(`onClick: (_ctx.value!)`)
  
  // Test TSInstantiationExpression  
  const { code: code2 } = compile(`<div @click="fn<string>"></div>`)
  expect(code2).toMatch(`onClick: (_ctx.fn<string>)`)
  
  // Test TSSatisfiesExpression
  const { code: code3 } = compile(`<div @click="obj satisfies Type"></div>`)
  expect(code3).toMatch(`onClick: (_ctx.obj satisfies Type)`)
})
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between d9bd436 and 575fc50.

⛔ Files ignored due to path filters (1)
  • packages/compiler-core/__tests__/transforms/__snapshots__/transformExpressions.spec.ts.snap is excluded by !**/*.snap
📒 Files selected for processing (2)
  • packages/compiler-core/__tests__/transforms/transformExpressions.spec.ts (1 hunks)
  • packages/compiler-core/src/transforms/transformExpression.ts (3 hunks)
🧰 Additional context used
🧬 Code Graph Analysis (1)
packages/compiler-core/src/transforms/transformExpression.ts (1)
packages/compiler-core/src/babelUtils.ts (1)
  • TS_NODE_TYPES (498-504)
⏰ Context from checks skipped due to timeout of 90000ms (3)
  • GitHub Check: Redirect rules
  • GitHub Check: Header rules
  • GitHub Check: Pages changed
🔇 Additional comments (3)
packages/compiler-core/src/transforms/transformExpression.ts (3)

21-21: LGTM! Import aligns with the TypeScript handling requirement.

The import of TS_NODE_TYPES is correctly placed and necessary for the TypeScript expression wrapping logic.


351-352: LGTM! Conditional wrapping logic is correctly implemented.

The logic properly checks if the AST node type requires wrapping (TypeScript expressions) and conditionally adds the opening parenthesis before processing identifiers. This ensures TypeScript syntax like type assertions are preserved in the generated code.


382-382: LGTM! Closing parenthesis correctly balances the opening one.

The conditional closing parenthesis properly balances the opening parenthesis added earlier, ensuring well-formed expressions in the generated code.

@zhiyuanzmj zhiyuanzmj changed the title fix(compiler-core): typed expressions should be wrapped in parentheses fix(compiler-core): remove types for expressions May 28, 2025
@edison1105 edison1105 added 🍰 p2-nice-to-have Priority 2: this is not breaking anything but nice to have it addressed. ready for review This PR requires more reviews labels May 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🍰 p2-nice-to-have Priority 2: this is not breaking anything but nice to have it addressed. ready for review This PR requires more reviews scope: compiler
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants