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

built-in-components/keepalive

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.

KeepAlive component props interface

KeepAlive accepts props: include (MatchPattern, optional) - if specified, only components with names matched by include will be cached; exclude (MatchPattern, optional) - components with names matched by exclude will not be cached; max (number | string, optional) - the maximum number of component instances to cache. MatchPattern is defined as string | RegExp | (string | RegExp)[].

KeepAlive component caching behavior

KeepAlive caches dynamically toggled components without destroying inactive component instances. There can only be one active component instance as the direct child of KeepAlive at any time.

KeepAlive lifecycle hooks activated and deactivated

When a component is toggled inside KeepAlive, its activated and deactivated lifecycle hooks will be invoked accordingly, providing an alternative to mounted and unmounted, which are not called. This applies to the direct child of KeepAlive as well as all its descendants.

Give your agent this brain