Manual:Coding conventions/Vue

This page describes coding conventions for Vue in the MediaWiki codebase. See also the JavaScript and CSS/LESS conventions which apply to such code within Vue files.

Linting
We use ESLint as our code quality tool, with the Vue profile within the custom config for Wikimedia.

Single-file Components
Vue's single-file components format (".vue") should be used wherever possible. This allows templates, logic, and (optionally) styles for a given component to live together in one file. ResourceLoader supports on-the-fly compilation of .vue files (see here for more info about using Vue with ResourceLoader ). This allows developers to write .vue files without needing to rely on any new build tools (Rollup, Webpack, etc), while still benefiting from the various optimizations that ResourceLoader provides for front-end code (RTL styling via CSS Janus, JS minification, etc).

Where possible, Vue code should follow the Vue community's style guide. In particular, all recommendations in "Priority A: Essential" should be followed at all times. Any MediaWiki-specific exceptions will be called out below.

General Structure
Single-file components are broken into three sections:,  , and  ; components should follow this order, with the   block being optional. Each component file should be listed individually under the  property in the appropriate module definition in. Make sure that the module definition also includes the  module as a dependency.

Template

 *  tags should contain a single root element
 * Component tags must not be self-closing: this is a departure from Vue's style guide recommendations based on current limitations in ResourceLoader. Regardless of whether a component uses slots, it should have a closing tag. This recommendation will likely change to conform to Vue's community style guilde once ResourceLoader has been updated to remove this limitation.
 * Use the directive short-hands ( instead of ,   instead of  ).
 * Elements with multiple attributes should break them out onto separate lines
 * Component templates should only include simple expressions; for anything more complex, define a computed property or method in the  section instead.
 * Message strings in templates must be internationalized just like in standard JS or PHP UI development. The  resource module in Core includes an i18n plugin that provides helper functions and directives to simplify this for most use-cases. These same methods are available programatically in the   section of a component by calling   (useful in computed properties that need to manipulate message strings before display, for example).
 * Message strings in templates must be internationalized just like in standard JS or PHP UI development. The  resource module in Core includes an i18n plugin that provides helper functions and directives to simplify this for most use-cases. These same methods are available programatically in the   section of a component by calling   (useful in computed properties that need to manipulate message strings before display, for example).

Script

 * Code should be written in ES5 and polyfills should be provided for any feature being utilized which may not be present in all Grade-A browsers of MediaWiki's browser support matrix  (which still includes IE11 at the time of writing)
 * Single-file components delivered via ResourceLoader should follow the CommonJS module format and should use ResourceLoader's PackageFiles feature . This means that each component file should include a   statement, and should import other code using
 * Component options should be specified in the order defined here: https://github.com/wikimedia/eslint-config-wikimedia/blob/master/vue-common.json. Generally this means:,  ,  ,  ,  ,   properties,  , watchers, lifecycle hooks, and finally render functions (in the rare situations where those need to be defined manually).
 * Render functions should be avoided outside of special cases; HTML-style templates are preferred instead. The  Resource Module provided in core is the full version, which includes the template compiler.
 * Use prop definitions and consider specifying defaults or validating data where necessary. Boolean props should have no default (they will implicitly default to falsy).
 * Avoid implicit parent-child communication and the mutation of received props within a child component. Prefer the "props down / events up" approach
 * Avoid implicit parent-child communication and the mutation of received props within a child component. Prefer the "props down / events up" approach

ES6/ResourceLoader
Coming soon!

Progressive Enhancement
TBD: define a no-JS fallback for most features you build this way.