apx

Build a full-stack Databricks App by using apx to organize backend API routes, wire React UI components with generated hooks, and manage local dev workflows. It enforces project patterns for Pydantic models, FastAPI routers, and Suspense-based data fetching.

Adding a FastAPI route requires following pattern-driven development: define Pydantic models, create FastAPI routers, regenerate OpenAPI schemas, and wire the React frontend to the newly generated query hooks using Suspense-based data loading.

Yes, apx works with shadcn/ui components and Suspense-based data fetching. It provides conventions for wiring React pages to generated query hooks and applying shadcn/ui components within your Databricks App frontend architecture.

Debug a Databricks App by managing local dev servers, checking logs, refreshing OpenAPI specifications, and validating changes using the recommended checks provided by the apx workflow before deployment.

Yes, you can inspect available endpoints and generated hooks before editing. apx provides API and route discovery features so you can quickly review existing FastAPI routes and React query hooks prior to backend or frontend modifications.

The best way to manage OpenAPI regeneration is through the apx dev server workflow, which handles refreshing OpenAPI schemas and validating changes after you update FastAPI routers or Pydantic models in your Databricks App.