Pick a focused question that fits your time, stack, and interview goal.
16 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 contextual sanitization and treats bypass APIs as narrow security-review decisions rather than general encoding helpers.
Connects environment and element injectors to instance lifetime, overrides, lazy routes, and accidental state isolation.
Chooses template-driven, typed reactive, or experimental Signal Forms based on workflow complexity and stability needs.
Uses ownership, inputs, outputs, rendering responsibility, and dependency scope to define maintainable standalone components.
Uses production build output, explicit budgets, dependency analysis, and meaningful lazy boundaries instead of arbitrary size cuts.
Overrides dependencies at the provider boundary while preserving the same injection scope and contract used in production.
Places each risk at the cheapest reliable test boundary and keeps a small set of browser journeys for integration confidence.
Uses supported version steps, ng update migrations, dependency compatibility, targeted cleanup, and staged production evidence.
Handles expected failures at their callsite and reserves ErrorHandler for reporting unexpected framework or global failures with useful context.
Tests rendered behavior, user interaction, outputs, and visible failure states without coupling to private implementation details.
Uses harnesses for reusable or complex widgets where a stable user-oriented test API is more valuable than direct DOM coupling.
Uses runtime tokens for configuration and abstractions while distinguishing provider recipes and instance identity.
Separates source state, derived state, and synchronization with external systems to prevent reactive loops.
Chooses between synchronous UI state and asynchronous event streams without treating either model as a replacement for the other.
Distinguishes one-way data, events, and deliberate two-way component contracts without hiding ownership.