apx

You build full-stack Databricks Apps with React and FastAPI using a convention-based project layout that combines Vite and TanStack Router with Pydantic models and dependency injection. This standardized workspace setup accelerates development and safe iteration.

To keep your OpenAPI TypeScript client in sync with FastAPI backend changes, you run the refresh_openapi tool via the apx CLI after editing backend routes. This deterministic dev loop ensures your frontend client accurately reflects the latest API signatures without brittle REST calls.

The correct workflow for integrating the Databricks SDK in a FastAPI backend involves following SDK-first rules and fetching Databricks SDK signatures via docs lookup. You manage backend and frontend integration tasks using these standardized conventions to avoid brittle REST calls and ensure accurate API usage.

You start and manage a local dev server for a React and FastAPI project using apx dev commands. This toolkit allows you to start, stop, restart, check, and inspect dev server logs while maintaining a deterministic development loop with synchronized OpenAPI client generation.

Yes, you can use apx for managing frontend UI components in a Databricks App. The toolkit supports creating and modifying shared UI components and frontend pages alongside API routes, ensuring full-stack integration within a single convention-based project layout.

Using a standardized toolkit for Databricks full-stack app development speeds up your workflow by providing deterministic dev loops and consistent conventions. It eliminates manual configuration errors by enforcing rules like routes-first development and automated OpenAPI client generation after backend changes.