v-html usages is replaced by a safer by default alternative. The goals are multiple: * make it easier to do the right thing for the developers: besides telling Vue to use the plugin at the instantiation of the app, the new directive can be used directly. There is no need of defining a new computed properties to sanize the value which means less boilerplate code. * reduce the number of points to inspect: only the directive/plugin code (and potentially a custom config at the init of the Vue app) instead of all the usages of v-html and the computed props associated with them. Note this does not means v-dompurify-html should be used everywhere, the usages should be limited where there is a real need for it and no alternative (same as v-html). No functionnal change is expected. vue-eslint-parser has been rollbacked to version 5.x. The 6.x version is not yet compatible with eslint-plugin-vue [0] causing false positives. It seems that major versions of vue-eslint-parser and eslint-plugin-vue must be kept in sync. [0] https://github.com/vuejs/eslint-plugin-vue/pull/807 Change-Id: Ibd599706cf3f6b19076841b4d7f330cab11e2e33

+86 −99

Author

Thomas Gerbet (tgerbet) 2019-04-15 08:56

Committer

Thomas Gerbet (tgerbet) 2019-04-18 17:31

Hash 66d5b3917b9b09f017ca90cc36e56e8602d15724

Parent e165b91f2efd0d16cd3cdf75db6e3393dc2c647e

Reference git #tuleap/stable/66d5b3917b9b09f017ca90cc36e56e8602d15724