databricks-app-apx

A full-stack Databricks app using APX requires a backend FastAPI service following a 3-model pattern and a React frontend. The skill enforces CRUD routes with explicit operation_id and response_model, driving frontend integration via OpenAPI client generation.

To generate an OpenAPI client for React, the APX workflow uses your FastAPI backend's OpenAPI schema. It enforces explicit operation_id and response_model on CRUD routes to automatically regenerate the frontend client and ensure type-safe API integration.

Yes, you can expand existing APX-based Databricks applications by adding CRUD routes. The skill enforces the 3-model backend pattern and requires explicit operation_id and response_model configurations to maintain OpenAPI-driven client generation.

The APX 3-model backend pattern is a structural requirement for FastAPI services on Databricks. It enforces specific model separation for CRUD routes, ensuring OpenAPI schemas correctly generate React frontend clients with explicit operation_id and response_model definitions.

Yes, the APX framework supports React frontend patterns including routing and Suspense. It scaffolds the frontend UI with these patterns integrated, alongside mock data and OpenAPI client generation, to rapidly prototype full-stack Databricks apps.

APX is limited to projects starting new or expanding existing Databricks applications using its specific FastAPI and React stack. It enforces strict workflow requirements like the 3-model backend pattern, meaning it cannot scaffold apps deviating from this architecture.