pre-commit

Author: samuelcolvin

distributed-frontend-example/.vscode/settings.json

@@ -1,3 +1,3 @@
 {
     "makefile.configureOnOpen": false
-}
+}

distributed-frontend-example/Makefile

@@ -4,9 +4,9 @@ install:
 	uv sync
 
 .PHONY: frontend-dev
-frontend-dev: 
+frontend-dev:
 	cd frontend && npm run dev
 
 .PHONY: backend-dev
-backend-dev: 
+backend-dev:
 	uv run main.py

distributed-frontend-example/README.md

@@ -11,7 +11,7 @@ specifics can be found in the `ClientInstrumentationProvider.tsx` file.
 
 For security/performance reasons, the browser instrumentation does not send traces to Logfire directly, but
 instead sends them to the backend. The backend then proxies the traces to
-Logfire - the `/client-traces` FastAPI endpoint in `main.py`. In that way, the Logfire write token is not exposed in the client-side bundle. 
+Logfire - the `/client-traces` FastAPI endpoint in `main.py`. In that way, the Logfire write token is not exposed in the client-side bundle.
 In production, you should ensure that the proxy endpoint is Auth protected and only accessible to your frontend.
 
 # Running the demo

distributed-frontend-example/frontend/src/index.css

@@ -99,4 +99,3 @@ button:disabled {
 .hidden {
   display: none;
 }
-