Vue JS Programming Standards 2

Question 1

Which naming convention does the official Vue style guide recommend for single-file component filenames?

Accepted Answer

PascalCase or kebab-case

Answer

Vue's style guide recommends component filenames be either consistently PascalCase or consistently kebab-case.

Question 2

Why does the Vue style guide require multi-word component names like 'TodoItem' instead of 'Todo'?

Accepted Answer

To avoid conflicts with existing and future HTML elements

Answer

Multi-word names prevent collisions with current or future standard HTML elements, which are all single-word.

Question 3

What is the recommended way to declare component props for clarity per Vue standards?

Accepted Answer

Use detailed object form with type and validation

Answer

Detailed prop definitions specifying type, required, and default improve readability and catch errors.

Question 4

Per the Vue style guide, why must 'v-for' always be paired with a 'key'?

Accepted Answer

To maintain internal component state and predictable DOM updates

Answer

A unique key helps Vue track node identity and preserves component state across re-renders.

Question 5

What does the Vue style guide say about using 'v-if' and 'v-for' on the same element?

Accepted Answer

Avoid it because their priority is ambiguous and it hurts readability

Answer

Combining them on one element is discouraged; filter via a computed property or wrap with a template instead.

Vue JS Practice Test