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
/nuxtPublic

test: add reproduction for #31569#31574

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
OrbisK wants to merge6 commits intonuxt:main
base:main
Choose a base branch
Loading
fromOrbisK:test/31569
Open

Conversation

@OrbisK
Copy link
Member

@OrbisKOrbisK commentedMar 28, 2025•
edited
Loading

🔗 Linked issue

#31569

📚 Description

This PR reproduces#31569. It does rename a file to the same resolved name and breaks.

I added both a HMR trigger (write to file) and refreshed the page.

@bolt-new-by-stackblitz
Copy link

Review PR in StackBlitz CodeflowRun & review this pull request inStackBlitz Codeflow.

@coderabbitai
Copy link

coderabbitaibot commentedMar 28, 2025•
edited
Loading

Walkthrough

The changes introduce new test cases and Vue components to verify the application's handling of file renaming. A new end-to-end test is added that navigates to a specific route, verifies the initial text of a component, renames a file from "test.vue" to "example-test.vue", updates the file content, and then checks that the updated text is displayed both immediately and after a page reload. Additionally, a new Vue component template is added in a fixture file to support the test, and a corresponding page component is introduced which utilises this updated component. These modifications ensure that the application correctly processes file renaming while maintaining consistent import names.

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between89f76f9 and7468b60.

📒 Files selected for processing (1)
  • test/fixtures/hmr/components/example/test.vue (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • test/fixtures/hmr/components/example/test.vue
⏰ Context from checks skipped due to timeout of 90000ms (2)
  • GitHub Check: build
  • GitHub Check: code
🪧 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.
    • 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 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 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 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 resolve resolve all the CodeRabbit review comments.
  • @coderabbitai plan to trigger planning for file edits and PR creation.
  • @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.

@pkg-pr-new
Copy link

pkg-pr-newbot commentedMar 28, 2025•
edited
Loading

Open in StackBlitz

@nuxt/kit

npm i https://pkg.pr.new/@nuxt/kit@31574

nuxt

npm i https://pkg.pr.new/nuxt@31574

@nuxt/rspack-builder

npm i https://pkg.pr.new/@nuxt/rspack-builder@31574

@nuxt/schema

npm i https://pkg.pr.new/@nuxt/schema@31574

@nuxt/vite-builder

npm i https://pkg.pr.new/@nuxt/vite-builder@31574

@nuxt/webpack-builder

npm i https://pkg.pr.new/@nuxt/webpack-builder@31574

commit:96b39a1

@codspeed-hq
Copy link

codspeed-hqbot commentedMar 28, 2025•
edited
Loading

CodSpeed Performance Report

Merging#31574 willnot alter performance

ComparingOrbisK:test/31569 (96b39a1) withmain (4b56bb9)

Summary

✅ 10 untouched benchmarks

Copy link
Member

@danielroedanielroe left a comment

Choose a reason for hiding this comment

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

thank you

OrbisK reacted with heart emoji
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@danielroedanielroedanielroe approved these changes

At least 1 approving review is required to merge this pull request.

Assignees

No one assigned

Labels

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@OrbisK@danielroe
[8]ページ先頭
©2009-2025 Movatter.jp