Vue framework tuning #1829
Description
Description of the enhancement
- Vue prints a "You are running a development build of Vue. Make sure to use the production build (*.prod.js) when deploying for production." in browser console.
- console.log() calls should be pruned from JS code
- Vue prints warnings for components that are not being loaded for the current page type. E.g. fron page console looks like:
vue.global.js:2263 [Vue warn]: Failed to mount app: mount target selector "#concept-mappings" returned null.
vue.global.js:2263 [Vue warn]: Failed to mount app: mount target selector "#resource-counts" returned null.
vue.global.js:2263 [Vue warn]: Failed to mount app: mount target selector "#term-counts" returned null.
vue.global.js:2263 [Vue warn]: Failed to mount app: mount target selector "#tab-alphabetical" returned null.
vue.global.js:2263 [Vue warn]: Failed to mount app: mount target selector "#tab-hierarchy" returned null.
vue.global.js:2263 [Vue warn]: Failed to mount app: mount target selector "#tab-groups" returned null.
vue.global.js:2263 [Vue warn]: Failed to mount app: mount target selector "#tab-changes" returned null.
vue.global.js:2263 [Vue warn]: Failed to mount app: mount target selector "#search-vocab" returned null.
Who are the users that would benefit from the enhancement and how?
Nice to have for everyone, now that we are moving towards production stage.
Why is the enhancement important?
This is cosmetic improvement, but it might save trouble from anyone developing Vue components for Skosmos (e.g. in plugin development).