How to implement a streamlined style in Vue (detailed tutorial)

<p>This article explains the relevant knowledge points of the Vue streamlined style and shares the example code. Interested friends can refer to it.

<p>The previous words

<p>The style guide on the Vue official website is classified according to priority (in order of necessary, strongly recommended, recommended, and used with caution), and the code intervals are large and difficult to query. This article is classified by type and reduces some examples or explanations. It is a streamlined version of the Vue style guide

<p>Component name

<p>[Component name is multiple words] (required)

<p>Component names should always be multiple words, except for the root component App. Doing so avoids conflicts with existing and future HTML elements, since all HTML element names are single-word names. , or always connected with a horizontal line (kebab-case)] (strongly recommended)

<p>[The basic component name must start with a specific prefix] (strongly recommended)

<p>Apply specific styles and conventions Base components (that is, presentational, non-logical, or stateless components) should all start with a specific prefix, such as Base, App, or V

<p> [Components that should only have a single active instance should Name it with the prefix

The<p> to show its uniqueness] (strongly recommended) This does not mean that the component can only be used on a single page, but

each page<p> Only used once, these components will never accept any prop

//bad
components/
|- MyButton.vue
|- VueTable.vue
|- Icon.vue
//good
components/
|- BaseButton.vue
|- BaseTable.vue
|- BaseIcon.vue

Copy after login

[Subcomponents that are tightly coupled with the parent component should be named with the parent component name as a prefix] (strongly recommended)

<p>[Component name It should start with a high-level (usually general description) word and end with a descriptive modifier] (strongly recommended)

<p>[The component name in single-file components and string templates should always be PascalCase ——But always kebab-case in DOM template] (strongly recommended)

<p>[Component names should tend to be complete words rather than abbreviations] (strongly recommended)

<p>Component related

<p>[Single file components, string templates and components without content in JSX should be self-closing - but don’t do this in DOM templates] (strongly recommended)

<p>Self-closing components mean that they are not only No content, and deliberately no content

<p>[Set scope for component styles] (required)

<p>This rule is only relevant for single-file components.

It is not necessary to <p> use the scoped feature. Scoping can also be set through CSS Modules, or using other libraries or conventions<div class="code" style="position:relative; padding:0px; margin:0px;"><pre class='brush:php;toolbar:false;'>//bad &lt;!-- 在单文件组件、字符串模板和 JSX 中 --&gt; &lt;MyComponent&gt;&lt;/MyComponent&gt; &lt;!-- 在 DOM 模板中 --&gt; &lt;my-component/&gt; //good &lt;!-- 在单文件组件、字符串模板和 JSX 中 --&gt; &lt;MyComponent/&gt; &lt;!-- 在 DOM 模板中 --&gt; &lt;my-component&gt;&lt;/my-component&gt;</pre><div class="contentsignin">Copy after login</div></div>[Single-file components should always keep the order of