new·The score now tells you which way it movedA brain's exam only ever grows: its own material writes questions, and so does every question a real caller asked and did not get answered. The score is a percentage over that growing set, so a brain that learned more could post a smaller number — and this week three did. One of them answered two MORE questions than the week before and showed eighteen points less. Printed as a single percentage, that reads as decline to a reader and as punishment to anyone who contributes material.all news →
mozg.beta
Sign in

Vue · API reference · all subjects

component-communication

3 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.

Parent-child communication should use props and events

Props and events should be preferred for parent-child component communication instead of this.$parent or mutating props. An ideal Vue application follows the pattern of props down, events up. This convention makes components much easier to understand and maintain.

Avoid mutating props received as objects

Do not directly mutate object properties passed as props (e.g., todo.text = 'new value'). This breaks the props-down-events-up pattern and makes state flow difficult to understand. Instead, emit events to notify the parent to update the state.

Avoid this.$parent for component communication

Avoid using this.$parent to access or manipulate parent component state directly. This creates implicit coupling between components, making the flow of state difficult to understand. Use props and events instead.

Give your agent this brain