Skip to content
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

Could not open [id].vue in the editor (on Windows/NTFS) #534

Closed
WebMechanic opened this issue Jul 20, 2024 · 1 comment
Closed

Could not open [id].vue in the editor (on Windows/NTFS) #534

WebMechanic opened this issue Jul 20, 2024 · 1 comment
Labels
duplicate This issue or pull request already exists upstream Related to an upstream issue

Comments

@WebMechanic
Copy link

Hello,
this is an excellent next version of the Vue Dev Tools. Very well done!
This might be the wrong repo as the origin of the error message below might come from a plugin. Please let me know so I can move this to the right place.

On Windows there seems to be an issue with Components (RouterView) that use VueRouter's "magic" properties in their file name like the sample "User ID" component from the router documentation [id].vue.
I have "vue-router": "^4.4.0" and "unplugin-vue-router": "^0.10.0" installed
grafik

If I click the HTML element generated by [id].vue I see this in the terminal

Could not open [id].vue in the editor.
When running on Windows, file names are checked against a safe file name pattern to protect against remote code execution attacks. File names may consist only of alphanumeric characters (all languages), periods, dashes, slashes, and underscores.

If I need brackets in the file name to make use of automagic RouterView props, how can I use this on Windows (NTFS) where brackets are not permitted?

  • can I use different characters than [] that'd do the trick and also work on Linux and Mac?
  • can this honourable safety check be disabled if the webpage runs on "localhost" (or a box on my LAN) where "remote code execution attacks" are very unlikely...

Thank you!

@alexzhang1030
Copy link
Member

Duplicate of #531

@alexzhang1030 alexzhang1030 marked this as a duplicate of #531 Jul 22, 2024
@alexzhang1030 alexzhang1030 added duplicate This issue or pull request already exists upstream Related to an upstream issue labels Jul 22, 2024
webfansplz added a commit that referenced this issue Jul 23, 2024
webfansplz added a commit that referenced this issue Jul 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists upstream Related to an upstream issue
Projects
None yet
Development

No branches or pull requests

3 participants