Actions

Actions are the only way to mutate state.

moon-spa uses setup(self, props) actions declared explicitly in actions or inferred from local callables when setup omits a return mapping.

Standard action pattern

class Counter(Component):
    def setup(self, props):
        state = {"count": 0, "visible": True}
        data = {"lastChange": "init"}

        def increment():
            state["count"] += 1
            data["lastChange"] = "increment"

        def decrement():
            state["count"] -= 1

        def reset():
            state["count"] = 0

        def flip():
            state["visible"] = not state["visible"]

Template binding:

<button @click="decrement">-</button>
<button @click="reset">0</button>
<button @click="increment">+</button>

Conditional actions

def increment():
    if state["count"] < 10:
        state["count"] += 1

For declarative operations, supported comparisons in cond are emitted as client-side guards: <, <=, >, >=, ==, !=.

Rules

• Define actions inside setup(self, props).
• You may omit returned actions mapping; server can infer actions from local functions.
• Functions named as lifecycle hooks (created, mounted, updated, unmounted) are inferred as lifecycle, not actions.
• Use callables when action logic should execute on server via server_call.
• Use mapping operations (set, add, sub, toggle, multi, log) for direct client-side behavior.
• Keep state mutations explicit and deterministic.
• If an action mutates data, the resulting data keys are patched to props automatically without return {...}.