▸case-01 I am building a React 18 application and need to set up a global user session store with persistence. Provide a complete Zustand store implementation with TypeScript. | pass→fail | 24,479 | 9,674 | -60% | 1 | 1 | 0% | 3,236 | 704 | -78% | 0 | 0 | — |
▸case-02 I am building an Angular 17 application and need to restrict access to the dashboard route using a functional route guard (`CanActivateFn`) that checks authentication status from an Auth service. Provide the route guard code. | pass→pass | 18,203 | 13,980 | -23% | 1 | 1 | 0% | 1,983 | 1,796 | -9% | 0 | 0 | — |
▸case-03 In an Angular 17 application, write a custom synchronous ValidatorFn for Reactive Forms that validates whether a form control value matches a specific password complexity regex. | pass→pass | 20,571 | 19,225 | -7% | 1 | 1 | 0% | 2,900 | 3,096 | +7% | 0 | 0 | — |
▸case-04 In an Angular 17 application, create a functional HttpInterceptorFn that appends a Bearer JWT token from local storage to outgoing HTTP requests. | pass→pass | 9,410 | 27,398 | +191% | 1 | 1 | 0% | 1,647 | 1,430 | -13% | 0 | 0 | — |
▸case-05 I have a standalone Angular 17 component that manages local toggle state and search filter input. A colleague suggested creating a BehaviorSubject with .asObservable() and using async pipes in the template. Provide the modern Angular 17+ idiomatic approach for local component state without RxJS subjects. | pass→pass | 19,930 | 18,110 | -9% | 1 | 1 | 0% | 2,464 | 2,489 | +1% | 0 | 0 | — |
▸case-06 In an Angular 17 component, I need to log changes to a `query` signal and launch an asynchronous search API call whenever `query` changes, while ensuring previous pending HTTP requests are cancelled or cleaned up. Someone suggested doing the API call inside `computed(() => fetch(this.query()))`. Show the correct Angular pattern for side effects triggered by signal changes. | fail→fail | 21,998 | 16,043 | -27% | 1 | 1 | 0% | 2,754 | 2,829 | +3% | 0 | 0 | — |
▸case-07 We are adding feature-level state management for an e-commerce shopping cart in an Angular 17 app. The cart needs to hold cart items, calculate total price, and support add/remove operations. Provide the modern lightweight NgRx `@ngrx/signals` SignalStore definition. | pass→pass | 35,905 | 20,332 | -43% | 1 | 1 | 0% | 3,007 | 2,994 | -0% | 0 | 0 | — |
▸case-08 In an Angular application managing a task list store, when a user toggles a task's completion status, we want instant UI feedback (optimistic update). If the backend API call fails, the state must revert back to its original state and show an error. Provide the implementation pattern for this optimistic update and error rollback strategy. | pass→pass | 23,424 | 18,762 | -20% | 1 | 1 | 0% | 3,215 | 3,649 | +13% | 0 | 0 | — |
▸case-09 We are migrating an existing Angular service that exposes an RxJS `Observable<User[]>` from an HTTP service into modern Signals so components can consume `users()` directly. How should `toSignal` be used inside a service class constructor vs inside a method, avoiding injection context runtime errors? | pass→pass | 21,555 | 70,877 | +229% | 1 | 1 | 0% | 2,653 | 2,768 | +4% | 0 | 0 | — |
▸case-10 We have an input text signal `searchQuery()` in Angular 17. We want to feed changes from this signal into an RxJS pipeline that applies `debounceTime(300)` and `switchMap()` for typeahead search HTTP requests. Show the idiomatic Angular rx-interop conversion. | pass→pass | 15,786 | 10,805 | -32% | 1 | 1 | 0% | 1,884 | 2,077 | +10% | 0 | 0 | — |
▸case-11 We are designing state architecture for an enterprise Angular application with 50+ feature modules. Explain when to use root-provided global stores versus component-provided local stores or `@ngrx/signals`, and provide the Angular dependency injection configuration (`providedIn: 'root'` vs component `providers: [...]`) for component-scoped state lifecycle. | pass→pass | 27,839 | 27,501 | -1% | 1 | 1 | 0% | 4,546 | 3,944 | -13% | 0 | 0 | — |
▸case-12 We have a legacy Angular component using `@ngrx/component-store`. We are refactoring to modern Angular 17+ Signal architecture. Show how to rewrite a ComponentStore state interface, selector (`select`), and updater (`updater`) using `@ngrx/signals` SignalStore. | pass→pass | 20,542 | 43,285 | +111% | 1 | 1 | 0% | 2,844 | 3,000 | +5% | 0 | 0 | — |
▸case-13 A developer in our team wrote `this.items().push(newItem)` and `this.user().name = 'Alice'` inside an Angular signal component, but the UI is not re-rendering reliably. Explain why this happens and show the correct immutable signal update syntax using `.update()` and `patchState`. | pass→pass | 19,628 | 14,793 | -25% | 1 | 1 | 0% | 2,458 | 2,598 | +6% | 0 | 0 | — |
▸case-14 In an Angular 17 SSR (Server-Side Rendering) application using Signals for state management, how do we transfer server-rendered state data to the client during hydration to avoid redundant HTTP requests on initial page load? | pass→pass | 22,193 | 52,991 | +139% | 1 | 1 | 0% | 2,994 | 3,123 | +4% | 0 | 0 | — |
▸case-15 We are using NgRx Store in an Angular 17 standalone application configured with `provideStore()`. How do we enable Redux DevTools for state inspection and time-travel debugging in development builds only? | pass→pass | 18,808 | 14,680 | -22% | 1 | 1 | 0% | 2,195 | 1,829 | -17% | 0 | 0 | — |
▸case-16 In `@ngrx/signals`, we have 5 different feature stores that require standard pagination state (`page`, `pageSize`, `totalItems`). Show how to create a custom reusable `signalStoreFeature` to share this state slice and methods across multiple stores. | pass→pass | 22,478 | 20,711 | -8% | 1 | 1 | 0% | 3,143 | 3,470 | +10% | 0 | 0 | — |
▸case-17 In an Angular application with multiple feature state stores, what is the recommended architecture for completely clearing user-sensitive cached state upon user logout without forcing a full browser window reload? | pass→pass | 29,669 | 45,568 | +54% | 1 | 1 | 0% | 3,922 | 3,278 | -16% | 0 | 0 | — |
▸case-18 An Angular application has a nested state object containing user settings: `{ profile: { notifications: { email: true, sms: false } } }`. Show how to update `email` to `false` immutably using Angular signal `.update()` and using `@ngrx/signals` `patchState` with `deepSignal` helpers. | pass→pass | 18,302 | 25,748 | +41% | 1 | 1 | 0% | 2,287 | 2,184 | -5% | 0 | 0 | — |
▸case-19 Inside an Angular `effect()`, we need to log analytics whenever `userActionSignal()` changes. The log function reads `currentUserSignal()`, but we DO NOT want changes in `currentUserSignal()` to trigger the effect. How do we read `currentUserSignal()` inside the effect without tracking it? | pass→pass | 12,212 | 13,093 | +7% | 1 | 1 | 0% | 1,037 | 1,209 | +17% | 0 | 0 | — |
▸case-20 An Angular template calls `getFilteredItems()` in its HTML template, which runs expensive array filtering operations on every change detection cycle. How should this be refactored using Angular Signals to achieve automatic memoization? | pass→pass | 17,200 | 18,668 | +9% | 1 | 1 | 0% | 2,088 | 2,270 | +9% | 0 | 0 | — |
▸case-21 We have an existing Angular app with an Akita store exposing `selectActive()` as an RxJS `Observable`. We want to consume this state in a new standalone component using Angular 17 Signals without rewriting the Akita store immediately. Show the interop code pattern. | pass→pass | 19,506 | 10,843 | -44% | 1 | 1 | 0% | 2,271 | 1,976 | -13% | 0 | 0 | — |
▸case-22 We have a signal holding a configuration object `configSignal = signal({ theme: 'dark', itemsPerPage: 10 })`. When we call `configSignal.set({ theme: 'dark', itemsPerPage: 10 })`, Angular triggers downstream computed signals because object reference changed. How do we configure custom equality logic on the signal? | pass→pass | 16,704 | 12,316 | -26% | 1 | 1 | 0% | 1,735 | 1,495 | -14% | 0 | 0 | — |
▸case-23 We are designing state management for an Angular 17 SaaS dashboard. We have three distinct state requirements: (1) a multi-tab UI widget with local collapse/expand state, (2) a complex feature module managing cart checkout with async steps and computed totals, and (3) a global user session & authorization context used app-wide. Recommend the appropriate Angular state architecture pattern for each level. | pass→pass | 32,031 | 26,650 | -17% | 1 | 1 | 0% | 4,490 | 4,998 | +11% | 0 | 0 | — |