Pick a focused question that fits your time, stack, and interview goal.
How much time do you have?
Show one-drill sessions you can finish now.
10 results across 1 active filter
Page 1 of 1
Separates projected caller-owned content from a component's own view and explains when queries are justified.
Explains the notification paths Angular relies on and designs components that do not depend on incidental global checks.
Uses input availability, rendering completion, cleanup, and SSR safety to choose lifecycle work deliberately.
Profiles real interactions to separate excessive change detection, expensive component work, layout cost, and network delay before optimizing.
Keeps server and client output compatible while isolating browser APIs, user state, and post-render integration.
Exercises signal-based component contracts through Angular bindings and waits for scheduled rendering before asserting.
Uses repeatable navigation, heap evidence, retained-object paths, and ownership checks to find subscriptions, listeners, and DOM retained past teardown.
Defers non-critical UI with deliberate triggers, placeholders, prefetching, and hydration behavior while protecting core interactions.
Finds missing render notifications that forced test change detection can hide and uses production-like stability checks.
Connects modern template blocks and stable list identity to DOM reuse, component state, and rendering correctness.