Depends function basics in FastAPI - Step-by-Step Execution

Concept Flow - Depends function basics

Define dependency function

↓

Use Depends() in path operation

↓

FastAPI calls dependency

↓

Dependency returns value

↓

Path operation receives value

↓

Return response using dependency value

This flow shows how FastAPI calls a dependency function using Depends(), passes its result to the path operation, and returns the response.

Execution Sample

FastAPI

from fastapi import FastAPI, Depends

app = FastAPI()

def get_query():
    return "hello"

@app.get("/")
async def read_root(q: str = Depends(get_query)):
    return {"message": q}

This code defines a dependency function get_query and uses Depends to inject its return value into the path operation.

Execution Table

Step	Action	Function Called	Return Value	Path Operation Parameter	Response
1	Request to '/' received	None	None	None	None
2	FastAPI calls dependency get_query()	get_query()	"hello"	q = "hello"	None
3	Path operation read_root called with q	read_root(q="hello")	None	q = "hello"	None
4	read_root returns response	read_root()	None	q = "hello"	{"message": "hello"}
5	Response sent to client	None	None	None	{"message": "hello"}

💡 Request handled and response returned using dependency value

Variable Tracker

Variable	Start	After Step 2	After Step 3	Final
q	None	"hello"	"hello"	"hello"

Key Moments - 3 Insights

Why does FastAPI call the dependency function before the path operation?

FastAPI calls the dependency function first to get the value it needs to pass as a parameter to the path operation, as shown in execution_table step 2.

How does the path operation receive the value from the dependency?

The dependency's return value is assigned to the parameter annotated with Depends(), so the path operation gets it as a normal argument (see execution_table step 3).

What happens if the dependency returns a different value?

The path operation will receive that new value instead, changing the response accordingly, as the variable 'q' tracks in variable_tracker.

Visual Quiz - 3 Questions

Look at the execution table, what value does the dependency function get_query() return at step 2?

A "world"

B "hello"

C None

D "fastapi"

💡 Hint

Check the 'Return Value' column at step 2 in the execution_table.

At which step does the path operation receive the dependency value as a parameter?

A Step 3

B Step 1

C Step 2

D Step 5

💡 Hint

Look at the 'Path Operation Parameter' column to see when 'q' is assigned.

If get_query() returned "fastapi", how would the response change in the execution table?

A Response would be empty

B Response would be {"message": "hello"}

C Response would be {"message": "fastapi"}

D Response would cause an error

💡 Hint

Refer to variable_tracker and execution_table response column to see how 'q' affects output.

Concept Snapshot

Depends function basics in FastAPI:
- Define a dependency function that returns a value.
- Use Depends() in path operation parameters to inject that value.
- FastAPI calls the dependency before the path operation.
- The path operation receives the dependency's return value as a normal argument.
- This helps reuse code and manage inputs cleanly.

Full Transcript

This visual execution trace shows how FastAPI uses the Depends function to manage dependencies. First, a dependency function get_query is defined that returns a string. When a request comes to the root path, FastAPI calls get_query to get its return value. Then it passes that value as the parameter 'q' to the path operation read_root. The path operation uses 'q' to build the response dictionary. Finally, the response is sent back to the client. The variable tracker shows how 'q' changes from None to 'hello'. Key moments clarify why FastAPI calls dependencies first and how values flow. The quiz tests understanding of these steps by referencing the execution table and variable tracker.

Practice

1. What is the main purpose of the Depends function in FastAPI?

easy

A. To create HTML templates

B. To define database models

C. To inject dependencies automatically into path operation functions

D. To handle HTTP status codes

Solution

1. Step 1: Understand what Depends does

   Depends is used to declare dependencies that FastAPI will automatically provide to your route functions.

2. Step 2: Identify the main use case

   It helps inject reusable code like authentication, database sessions, or other shared logic into routes.

3. Final Answer:

   To inject dependencies automatically into path operation functions -> Option C

4. Quick Check:

   Depends injects dependencies = C [OK]

Hint: Depends injects reusable code into routes automatically [OK]

Common Mistakes:

• Confusing Depends with database or template functions
• Thinking Depends handles HTTP status codes
• Assuming Depends creates models

2. Which of the following is the correct way to declare a dependency in a FastAPI route using Depends?

easy

A. def read_items(db=Depends(get_db)): pass

B. def read_items(db: Depends(get_db)): pass

C. def read_items(db: Depends = get_db): pass

D. def read_items(db=Depends): pass

Solution

1. Step 1: Recall Depends syntax

   The correct syntax is to assign the parameter a default value of Depends with the dependency function inside.

2. Step 2: Match the correct option

   def read_items(db=Depends(get_db)): pass uses db=Depends(get_db), which is the proper way to declare a dependency.

3. Final Answer:

   def read_items(db=Depends(get_db)): pass -> Option A

4. Quick Check:

   Depends usage = parameter=Depends(function) [OK]

Hint: Use parameter=Depends(function) to declare dependencies [OK]

Common Mistakes:

• Using type annotation instead of default value for Depends
• Passing Depends without parentheses
• Assigning Depends without a function

3. Given the code below, what will be the output when accessing the /items/ endpoint?

from fastapi import FastAPI, Depends

app = FastAPI()

def get_number():
    return 42

@app.get('/items/')
def read_items(number: int = Depends(get_number)):
    return {"number": number}

medium

A. {"number": "get_number"}

B. {"number": 42}

C. Error: missing required parameter

D. {"number": null}

Solution

1. Step 1: Understand dependency injection

   The get_number function returns 42, and FastAPI injects this value into the number parameter.

2. Step 2: Check the returned response

   The route returns a dictionary with key "number" and value 42, so the output is {"number": 42}.

3. Final Answer:

   {"number": 42} -> Option B

4. Quick Check:

   Depends injects 42 = {"number": 42} [OK]

Hint: Depends calls function and injects return value [OK]

Common Mistakes:

• Expecting the function name instead of its return value
• Thinking parameter is missing if not passed explicitly
• Assuming null is returned if no argument given

4. What is wrong with the following FastAPI code using Depends? How to fix it?

from fastapi import FastAPI, Depends

app = FastAPI()

def get_user():
    return "Alice"

@app.get('/user/')
def read_user(user: str = Depends):
    return {"user": user}

medium

A. Depends is missing the dependency function; fix by using Depends(get_user)

B. The route path is invalid; fix by changing '/user/' to '/users/'

C. The return type is wrong; fix by returning a list instead of dict

D. The function get_user should accept parameters; fix by adding parameters

Solution

1. Step 1: Identify the Depends usage error

   The parameter uses Depends without specifying the dependency function, which is incorrect.

2. Step 2: Correct the Depends syntax

   It should be Depends(get_user) to tell FastAPI which function to call for the dependency.

3. Final Answer:

   Depends is missing the dependency function; fix by using Depends(get_user) -> Option A

4. Quick Check:

   Depends needs function argument = Depends(get_user) [OK]

Hint: Always pass the dependency function inside Depends() [OK]

Common Mistakes:

• Using Depends without parentheses or function
• Changing route path unnecessarily
• Changing return type without reason

5. How can you use Depends to share a database session across multiple routes without repeating code? Choose the best approach.

hard

A. Use Depends without any function to automatically get the session

B. Pass the session as a global variable to all routes

C. Manually create a session inside each route function

D. Create a function that returns the session and use Depends on it in each route

Solution

1. Step 1: Understand code reuse with Depends

   Depends allows you to write a function that creates or yields a database session once and injects it wherever needed.

2. Step 2: Identify the best practice

   Creating a session function and using Depends on it in routes avoids repetition and manages session lifecycle cleanly.

3. Final Answer:

   Create a function that returns the session and use Depends on it in each route -> Option D

4. Quick Check:

   Use Depends with session function for reuse = D [OK]

Hint: Use Depends with a session function to share DB session [OK]

Common Mistakes:

• Using global variables for sessions (not safe)
• Creating sessions manually in every route (repetitive)
• Using Depends without specifying a function