Why Sub-dependencies in FastAPI? - Purpose & Use Cases

The Big Idea

Discover how sub-dependencies can save you from tangled, repetitive code in FastAPI!

The Scenario

Imagine building a web app where multiple parts need user info, database access, and logging. You write code to get these for each part separately.

The Problem

Manually passing user info, database connections, and logs everywhere is tiring and easy to mess up. It leads to repeated code and bugs when you forget to pass something.

The Solution

FastAPI's sub-dependencies let you define small reusable pieces that automatically provide needed data or services. They connect smoothly, so each part gets exactly what it needs without extra work.

Before vs After

✗ Before

def endpoint(user=Depends(get_user), db=Depends(get_db), logger=Depends(get_logger)):
    # repeated calls and passing
    pass

✓ After

def common_deps(user=Depends(get_user), db=Depends(get_db), logger=Depends(get_logger)):
    return user, db, logger

def endpoint(deps=Depends(common_deps)):
    user, db, logger = deps
    pass

What It Enables

This makes your code cleaner, easier to maintain, and lets you build complex dependency chains effortlessly.

Real Life Example

In a social media app, many routes need the current user and database. Using sub-dependencies, you write this once and reuse it everywhere, saving time and avoiding mistakes.

Key Takeaways

Manual passing of shared resources is repetitive and error-prone.

Sub-dependencies let you bundle and reuse common dependencies easily.

This leads to cleaner, more maintainable FastAPI code.