PHPAML

Documentation · Chapter 10

Inspect Engine instead of guessing.

This laboratory uses browser tools and Engine diagnostics to prove which work stays local and which work calls the server.

Every lesson starts from the problem, explains the mechanism, then gives a concrete verification.

Inspect clicks

Open Network, click a local counter ten times, and confirm no application request. Inspect the state attribute and updated text.

phpaml — zsh
1. Clear Network
2. Click local action
3. Trigger Api::get
4. Compare requests
5. Test offline and 404

Inspect an API action

Trigger Api::get and confirm exactly one request, loading state, response binding, and visible failure message.

Test failure paths

Disconnect the network, navigate to a missing route, and trigger a rejected API call. Verify Error and NotFound states rather than silent failure.

SUMMARY

What to remember

  • Engine runs a documented compiled subset, never arbitrary PHP.
  • Local actions avoid unnecessary server requests.
  • Effects coordinate time and asynchronous work.
  • Navigation, persistence, and shared context remain explicit.