Djungo Playground — Part 19

Frontend state synchronization: after every mutation, the interface should converge back to the backend state.
This chapter focuses on keeping form, viewer, and active filters aligned.

Config

apiKey (required for insert / getById / update / delete)

Recommended flow: load an entity, mutate it, and verify that the viewer refreshes while preserving the current query context.

Insert

year (required)

nation (optional)

title (required) url (optional) rating (optional)

After insert, the returned id is written back into the ID field and the viewer reloads with the current filters still active.

Read / Update / Delete by ID

Use getById before mutating a record. The form should reflect backend-confirmed state, not remembered assumptions.

After update, the form remains anchored to the same identity and the viewer reloads.
After delete, the form is cleared because the current working entity is no longer valid in the active workflow.

Query filters for view

title contains

nation equals

rating equals

limit

Active filters define the current query context. That context should survive insert, update, and delete.

Viewer (synchronized filtered result set)

The viewer always reloads from backend-driven state, never from remembered local assumptions.

Response