Fix suggested FastAPI middleware installation order

Unlike e.g. Django (or Express) FastAPI executes the middlewares so that
the first middleware that was added gets executed last and the last
middleware gets executed as the first/outermost one.

Author: ruohola

CHANGELOG.md

@@ -7,6 +7,10 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+### Fixed
+
+- Fix FastAPI middleware suggested installation order; it should ideally be the *last* one added.
+
 ## [1.5.0] - 2022-03-17
 
 ### Added

README.md

@@ -54,7 +54,7 @@ from fastapi import FastAPI
 
 app = FastAPI()
 
-# Ideally the first middleware you add.
+# Ideally the last middleware you add.
 app.add_middleware(ApilyticsMiddleware, api_key=os.getenv("APILYTICS_API_KEY"))
 ```
 

apilytics/fastapi.py

@@ -12,7 +12,7 @@ class ApilyticsMiddleware(starlette.middleware.base.BaseHTTPMiddleware):
     """
     FastAPI middleware that sends API analytics data to Apilytics (https://apilytics.io).
 
-    This should ideally be the first middleware you add to your app.
+    This should ideally be the last middleware you add to your app.
 
     Examples:
         main.py::