Vue JS Programming Standards 5

Question 1

Per Vue standards, why is it recommended to use PascalCase for component tags in SFC templates?

Accepted Answer

It distinguishes components from native HTML elements and aids editor support

Answer

PascalCase in single-file component templates clearly separates Vue components from HTML elements.

Question 2

What does the style guide recommend when a component grows too large?

Accepted Answer

Extract logical pieces into smaller child components or composables

Answer

Breaking large components into focused units improves reusability and maintainability.

Question 3

Why does Vue 3 discourage heavy reliance on global mixins for shared logic?

Accepted Answer

They cause naming collisions and unclear sources; composables are preferred

Answer

Mixins obscure where properties come from, so Composition API composables are recommended instead.

Question 4

Per standards, how should empty props or attribute values be handled for boolean props?

Accepted Answer

A present prop with no value implies true

Answer

A boolean prop written without a value is treated as true, matching HTML boolean attribute behavior.

Question 5

What is the recommended approach for handling form input binding consistently in Vue?

Accepted Answer

Use v-model for two-way binding on form elements

Answer

v-model provides standardized two-way binding and reduces boilerplate on form controls.

Vue JS Practice Test