You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It could be useful to ignore components given a pattern. e.g. src/routes/_not-a-page.vue, or .not-a-page or __not-a-page, etc but at the same time this can be achieved with the exclude option so is this really necessary?
The text was updated successfully, but these errors were encountered:
I think it's worth adding a default value to exclude and let users override this if necessary. As for the convention, a file or folder starting with _ seems like an easy choice since URL usually do not start with a _. It still requires the option to be overridden for edge cases:
exclude: ['**/_*',// files'**/_*/**, // folders '!_not-ignored',// _not-ignored should still be handled]
It could be useful to ignore components given a pattern. e.g.
src/routes/_not-a-page.vue
, or.not-a-page
or__not-a-page
, etc but at the same time this can be achieved with theexclude
option so is this really necessary?The text was updated successfully, but these errors were encountered: