feat(component): Add support for better naming of /index.vue
components
#1994
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR relates to vuejs/devtools#387. Sometimes developers have components nested inside directories and follow classic Node approach of naming them
/index.${extenstion}
, in this case/index.vue
. Devtools currently display every component as<Index>
unless you specifyname
. This PR will check for those components and use parent directory as component name.Example
Compnent is defined in
src/IndexComponent/index.vue
Before:
After:
Additional context
I’ve also taken the chance to use
basename
function from@vue/shared-utils
and removed same command form Vue 3 backend namespace.What is the purpose of this pull request?
Before submitting the PR, please make sure you do the following
fixes #123
).