1đź‘Ť
If you are using vue.js
this is certainly be a bad practice because in vue
custom tags are always an imported component which is registered locally or globally. Also, say that you are working with team of vue
developer and they have no idea where the hell t-card
component file is located?
👤Syed
- [Vuejs]-Vue: Detect when new component is mounted
- [Vuejs]-How to customize php artisan ui vue –auth files
0đź‘Ť
It’s not a good coding practice. It is confusing for others and also it “hides” information. For example if there is a class called “card”, you know that you (can) have multiple elements with that class. If the id is “card” you know that there can be only one element. If you do <t-card></t-card>
you don’t know that.
👤Mointy
- [Vuejs]-How to update the dist folder of Vue js without running npm run build a second time
- [Vuejs]-Vue, sharing blade/view with two routes
Source:stackexchange.com