📝 Docs preview for commitc9d3b22 at:https://63ccee9f0fb8da5c9c02fac2--fastapi.netlify.app

📝 Docs preview for commitdc6946f at:https://63ccf0f8cf78ab6745a882e4--fastapi.netlify.app

I understand the suggestion for "2", however I suggest not making those changes because that code is repeated in multiple places throughout the tutorials. As I understand the tutorials, they build on each other somewhat, and they focus on specific items in each section. It seems to me that making these changes in a few places adds inconsistencies that the learner has to investigate as they change. It may be more useful to keep it consistent even if the example isn't optimal?

@Ryandaydev First time when learner see thisq parameter in this articlehttps://fastapi.tiangolo.com/tutorial/query-params/#optional-parameters . And here it looks logical becauseq is optional and code example hasif condition for that parameter. For consisten I suggest addNone forq param inside annotations. After thisif statement make sense. And it will look like previous examples withq param:

@app.get("/items/{item_id}")asyncdefread_items(q:str|None,item_id:int=Path(title="The ID of the item to get")):results= {"item_id":item_id}ifq:results.update({"q":q})returnresults

📝 Docs preview for commit2bfa458 at:https://64697a4de93dbc10f72678bd--fastapi.netlify.app

Ok. I removed controversial changes and left only renamed functions

Nice, makes sense, thank you@OttoAndrey! 🍰

And thanks everyone for the input! ☕