Cookbook

Use the cookbook when you have a concrete problem and need a working pattern. Start with debugging if AngularTS is new to you. Every progressive recipe ends with a task to apply and checks that prove it worked.

Find recipes by area

Start with beginner recipes, then choose forms, HTTP, DOM updates, security, performance, data correctness, navigation, operations, or advanced browser work.

Choose who owns the result

Start from the result your application needs, not from a directive name.

Prefer the first applicable row. Do not introduce a client route or shared data service when one server response and one declarative interaction solve the problem.

Start here

1. Debug a running application
2. Select an element with ng-el
3. Pass server data without another request
4. Update existing DOM from state
5. Replace DOM from state
6. Swap server-rendered HTML
7. Run effects outside the DOM
8. Handle events
9. Build and submit forms
10. Read, write, and prefetch REST data
11. Authenticate requests
12. Cache REST reads
13. Add browser-owned routes

Change server data

Data correctness: handle uniqueness races, submit money safely, send dates with zones, and keep identifiers opaque.

HTTP behavior: revalidate with ETag, serve maintenance responses, validate return redirects, standardize errors, and negotiate page or fragment.

Browser and content security: sanitize rich text, deploy CSP, harden session cookies, support password managers, and redact secrets.

Interaction details: focus the first error, design an empty state, and preserve focus after swaps.

Transaction workflows: respect rate limits, run background jobs, make critical writes idempotent, save multi-step forms, and apply bulk actions.

Account and record workflows: archive and restore, handle permission rejection, keep filters in the URL, and log out safely.

Production form workflows: show server validation, send CSRF proof, confirm deletion, and resolve concurrent edits.

Production response workflows: retry a failed read, paginate on the server, download with the browser, and swap trusted server HTML.

Keep important forms usable with progressive enhancement, and define their HTTP response contracts before wiring the success and failure branches.

Load and navigate faster

Add specialized browser behavior

• Make a server-driven interaction accessible
• Load content near the viewport
• Receive live server events
• Exchange live messages with WebSocket
• Move measured CPU work to a worker
• Call an existing WebAssembly module
• Build a smaller production runtime
• Understand the similarity to HTMX

Integrate another framework

Start with the integration decision guide, then use the event bus for transient messages, ng-observe for reflected web-component attributes, or a shared application model for current reactive state.

Diagnose a production problem

Production change management: deliver server flags, record audit events, and roll contracts out compatibly.

When an API must use another origin, follow the cross-origin request recipe before adding browser workarounds.

Make failures traceable with a request ID, then run the shipping check against the complete interaction.

Trace one interaction with the HTTP debugging recipe, then control repeated requests only after measuring them. Before shipping, audit the full server-driven interaction.