Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings
/corePublic

feat(compiler-dom): support customizable select#13616

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Open
kovsu wants to merge1 commit intovuejs:main
base:main
Choose a base branch
Loading
fromkovsu:fix-#13608

Conversation

kovsu
Copy link
Contributor

@kovsukovsu commentedJul 11, 2025
edited by edison1105
Loading

close#13608

BeforeAfter
CleanShot 2025-07-11 at 11 29 01CleanShot 2025-07-11 at 11 29 18

Summary by CodeRabbit

  • Bug Fixes
    • Improved HTML validation to prevent unnecessary warnings when using<select> with<option> elements and when nesting elements inside<option>.
  • Tests
    • Added test cases to ensure no warnings are emitted for valid<select><option></option></select> and<option><p></p></option> structures.

@coderabbitaicoderabbitai
Copy link

coderabbitaibot commentedJul 11, 2025
edited
Loading

Walkthrough

The changes update HTML nesting validation logic by removing specific child element restrictions forselect,optgroup, andoption elements. Corresponding tests are added to confirm that no warnings are emitted for certain valid and previously restricted HTML nesting scenarios.

Changes

File(s)Change Summary
packages/compiler-dom/src/htmlNesting.tsRemovedselect,optgroup, andoption from theonlyValidChildren map, loosening child restrictions.
packages/compiler-dom/tests/transforms/validateHtmlNesting.spec.tsAdded tests to verify no warnings for<select><option></option></select> and<option><p></p></option>.

Poem

In the land of tags, the rules have eased,
Selects and options now nest as they please.
No warnings arise, the compiler’s content,
As rabbits rejoice in HTML’s intent.
With boundaries gone, the markup can play,
Hopping through elements in a friendlier way! 🐇

✨ 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 withCodeRabbit:

  • 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 oursupport 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 togenerate 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 theconfiguration 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 ourDocumentation for detailed information on how to use CodeRabbit.
  • Join ourDiscord Community to get help, request features, and share feedback.
  • Follow us onX/Twitter for updates and announcements.

@github-actionsGitHub Actions
Copy link

Size Report

Bundles

FileSizeGzipBrotli
runtime-dom.global.prod.js101 kB38.4 kB34.5 kB
vue.global.prod.js159 kB58.5 kB52.1 kB

Usages

NameSizeGzipBrotli
createApp (CAPI only)46.5 kB18.2 kB16.7 kB
createApp54.5 kB21.2 kB19.4 kB
createSSRApp58.7 kB22.9 kB20.9 kB
defineCustomElement59.5 kB22.8 kB20.8 kB
overall68.5 kB26.4 kB24 kB

@pkg-pr-newpkg.pr.new
Copy link

Open in StackBlitz

@vue/compiler-core

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

@vue/compiler-dom

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

@vue/compiler-sfc

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

@vue/compiler-ssr

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

@vue/reactivity

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

@vue/runtime-core

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

@vue/runtime-dom

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

@vue/server-renderer

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

@vue/shared

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

vue

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

@vue/compat

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

commit:075edae

Copy link

@coderabbitaicoderabbitaibot 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: 1

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between347ef1d and075edae.

📒 Files selected for processing (2)
  • packages/compiler-dom/__tests__/transforms/validateHtmlNesting.spec.ts (1 hunks)
  • packages/compiler-dom/src/htmlNesting.ts (0 hunks)
💤 Files with no reviewable changes (1)
  • packages/compiler-dom/src/htmlNesting.ts
🧰 Additional context used
🧬 Code Graph Analysis (1)
packages/compiler-dom/__tests__/transforms/validateHtmlNesting.spec.ts (1)
packages/compiler-dom/src/index.ts (1)
  • compile (41-64)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)
  • GitHub Check: Redirect rules
  • GitHub Check: Header rules
  • GitHub Check: Pages changed

Comment on lines +14 to +20
it("Don't warn with customize select and option", () => {
let err: CompilerError | undefined
compile(`<select><option></option></select>`, { onWarn: e => (err = e) })
compile(`<option><p></p></option>`, { onWarn: e => (err = e) })
expect(err).toBeUndefined()
})

Choose a reason for hiding this comment

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

⚠️ Potential issue

Fix test logic and improve test structure.

The test has a potential issue where theerr variable is shared between two compile calls, which could lead to false test results. If the first compile call generates a warning but the second doesn't, the test would incorrectly pass.

Additionally, the test name has grammatical issues and should be corrected.

Apply this diff to fix the test logic and improve the structure:

-  it("Don't warn with customize select and option", () => {+  it("should not warn with customizable select and option", () => {     let err: CompilerError | undefined     compile(`<select><option></option></select>`, { onWarn: e => (err = e) })+    expect(err).toBeUndefined()++    err = undefined // Reset for next test     compile(`<option><p></p></option>`, { onWarn: e => (err = e) })     expect(err).toBeUndefined()   })

Alternatively, consider splitting this into two separate test cases for better clarity and isolation:

-  it("Don't warn with customize select and option", () => {-    let err: CompilerError | undefined-    compile(`<select><option></option></select>`, { onWarn: e => (err = e) })-    compile(`<option><p></p></option>`, { onWarn: e => (err = e) })-    expect(err).toBeUndefined()-  })+  it('should not warn with customizable select', () => {+    let err: CompilerError | undefined+    compile(`<select><option></option></select>`, { onWarn: e => (err = e) })+    expect(err).toBeUndefined()+  })++  it('should not warn with customizable option', () => {+    let err: CompilerError | undefined+    compile(`<option><p></p></option>`, { onWarn: e => (err = e) })+    expect(err).toBeUndefined()+  })
📝 Committable suggestion

‼️IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
it("Don't warn with customize select and option",()=>{
leterr:CompilerError|undefined
compile(`<select><option></option></select>`,{onWarn:e=>(err=e)})
compile(`<option><p></p></option>`,{onWarn:e=>(err=e)})
expect(err).toBeUndefined()
})
it("should not warn with customizable select and option",()=>{
leterr:CompilerError|undefined
compile(`<select><option></option></select>`,{onWarn:e=>(err=e)})
expect(err).toBeUndefined()
err=undefined// Reset for next test
compile(`<option><p></p></option>`,{onWarn:e=>(err=e)})
expect(err).toBeUndefined()
})
🤖 Prompt for AI Agents
In packages/compiler-dom/__tests__/transforms/validateHtmlNesting.spec.ts aroundlines 14 to 20, the test shares the same error variable between two compilecalls, which can cause false positives if the first call sets an error but thesecond does not. To fix this, separate the tests into two distinct test caseseach with its own error variable to isolate warnings properly. Also, rename thetest to correct the grammar for clarity, for example, change "Don't warn withcustomize select and option" to "Does not warn with customized select andoption."

@edison1105edison1105 added version: minor 🍰 p2-nice-to-havePriority 2: this is not breaking anything but nice to have it addressed. labelsJul 16, 2025
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers

@coderabbitaicoderabbitai[bot]coderabbitai[bot] left review comments

Assignees
No one assigned
Labels
🍰 p2-nice-to-havePriority 2: this is not breaking anything but nice to have it addressed.version: minor
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

New allowed HTML Tags as children for<SELECT> and<OPTION>, anddata-allow-mismatch does not remove warning
2 participants
@kovsu@edison1105

[8]ページ先頭

©2009-2025 Movatter.jp