Skip to content

fix(docs): fix broken link to TypeScript Vue Plugin in console/atest-ui/README.md #731

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
merged 6 commits into from
Jun 30, 2025

Conversation

user-xixiboliya
Copy link
Contributor

What type of PR is this?
Very minor fix(docs): fix broken link to TypeScript Vue Plugin in console/atest-ui/README.md.

What this PR does / why we need it:
The old vscode‑typescript‑vue‑plugin (sometimes called “TypeScript Vue Plugin (Volar)”) has been removed and is no longer needed as a separate installation.

Volar (now the “Vue – Official” extension) includes all its features
The Vue team merged TypeScript support for Vue directly into Volar, making the separate plugin redundant.link to reddit

Copy link

@LinuxSuRen LinuxSuRen added documentation Improvements or additions to documentation skip-changelog labels Jun 30, 2025
Copy link
Owner

@LinuxSuRen LinuxSuRen left a comment

Choose a reason for hiding this comment

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

LGTM

However, please always create a new corresponding branch for each PR. See also the following explanation:

@LinuxSuRen LinuxSuRen merged commit 0c7d21a into LinuxSuRen:master Jun 30, 2025
14 checks passed
@LinuxSuRen
Copy link
Owner

It will bring unrelated commits into your PRs if you use master or another some branch every time. See the screenshots

image

@user-xixiboliya
Copy link
Contributor Author

user-xixiboliya commented Jun 30, 2025

Thank you for the reply. I have read the relevant guide in detail and studied the corresponding specifications. For example, currently, all changes in the repository I forked have been committed to the master branch. The next step should be to create a new local branch named fix-xxx-bug to make modifications, push it to my forked repository, and then submit a PR for the changes in this newly created fix-xxx-bug branch to the original repository.

I have a few small questions: I noticed that Dependabot is responsible for many branches in the original repository. It seems amazing to learn about Dependabot's related technologies and the role of maintaining so many branches.

Thanks again for your reply!

@LinuxSuRen
Copy link
Owner

Yes, some bots are helpful. The dependabot can find the latest dependencies. But we need to be careful before merging the dependency update.

@LinuxSuRen LinuxSuRen added the ospp 开源之夏 https://summer-ospp.ac.cn/ label Jun 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation ospp 开源之夏 https://summer-ospp.ac.cn/ skip-changelog
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants