스타일 가이드 - 베이스 컴포넌트 이름

[Bogyie]

• Deleted paragraph compare to https://v2.vuejs.org/v2/style-guide/
  

  kr.vuejs.org/src/v2/style-guide/index.md

  Lines 775 to 789 in 5413f53

  	- Since these components are so frequently used, you may want to simply make them global instead of importing them everywhere. A prefix makes this possible with Webpack:
  	``` js
  	var requireComponent = require.context("./src", true, /^Base[A-Z]/)
  	requireComponent.keys().forEach(function (fileName) {
  	var baseComponentConfig = requireComponent(fileName)
  	baseComponentConfig = baseComponentConfig.default || baseComponentConfig
  	var baseComponentName = baseComponentConfig.name || (
  	fileName
  	.replace(/^.+\//, '')
  	.replace(/\.\w+$/, '')
  	)
  	Vue.component(baseComponentName, baseComponentConfig)
  	})
  	```

• 스타일 가이드 - 베이스 컴포넌트 이름 [문단 삭제] #51 Not translated
  

  kr.vuejs.org/src/v2/style-guide/index.md

  Lines 748 to 775 in 6df59ee

  	### 베이스 컴포넌트 이름 <sup data-p="b">매우 추천함</sup>
  	**Base components (a.k.a. presentational, dumb, or pure components) that apply app-specific styling and conventions should all begin with a specific prefix, such as `Base`, `App`, or `V`.**
  	{% raw %}
  	<details>
  	<summary>
  	<h4>자세한 설명</h4>
  	</summary>
  	{% endraw %}
  	These components lay the foundation for consistent styling and behavior in your application. They may **only** contain:
  	- HTML elements,
  	- other base components, and
  	- 3rd-party UI components.
  	But they'll **never** contain global state (e.g. from a Vuex store).
  	Their names often include the name of an element they wrap (e.g. `BaseButton`, `BaseTable`), unless no element exists for their specific purpose (e.g. `BaseIcon`). If you build similar components for a more specific context, they will almost always consume these components (e.g. `BaseButton` may be used in `ButtonSubmit`).
  	Some advantages of this convention:
  	- When organized alphabetically in editors, your app's base components are all listed together, making them easier to identify.
  	- Since component names should always be multi-word, this convention prevents you from having to choose an arbitrary prefix for simple component wrappers (e.g. `MyButton`, `VueButton`).
  	- Since these components are so frequently used, you may want to simply make them global instead of importing them everywhere. A prefix makes this possible with Webpack:

[Mccreate]

I tried to translate this. 👀