policydb-route-patterns

FastAPI evaluates routes in registration order, so parameterized paths can shadow literal paths. You must register literal routes before parameterized routes to prevent misrouting and resolve 404 capture issues.

Standardize PATCH cell-save responses by returning JSON with ok and formatted fields. This provides consistent contracts for inline edits, enabling seamless UI updates without template rendering inconsistencies.

Configure HTMX row edit endpoints by providing endpoint variants for client detail, dashboard, and renewals views. Apply consistent templates across all variants to ensure uniform behavior and UI rendering.

Ensure templates receive required context by passing config-derived lists like renewal_statuses and opportunity_statuses. Route handlers must supply this configuration data to templates to avoid rendering errors.

Yes, you can use the literals-first route ordering pattern to debug 404 capture issues on existing policy routes. Reordering routes ensures literal paths are matched before parameterized paths intercept requests.

No specific external dependencies are required to implement these FastAPI endpoint patterns. The rules apply to standard FastAPI route definitions using built-in routing, HTMX integration, and PATCH response mechanisms.