🚀 Roadmap

[tiangolo]

Description

This is a tentative roadmap, I will update it as things evolve. Some things might be discarded, others might be added later. I didn't want to make it fully public as it could raise expectations, but it seems it would be more beneficial for the community to know all the ideas and objectives.

Work on this is alternated (and sometimes mixed) with work on FastAPI, SQLModel, Asyncer, and others.

Answering questions, issues, and PRs is also intermixed with this, but as in some cases one of these features would solve several issues or questions, or potentially solve something done by one or more PRs, in many cases I focus on this a bit more than on answering specific issues, questions, PRs.

Maintenance

The word "maintenance" or "maintainer" doesn't have a very strict definition, and it probably varies a lot from perspective.

A lot of the work related to maintaining FastAPI is done by contributors by answering questions, reviewing PRs, etc.

You can help me ensure each existing PR is in shape (has tests, solves the problem, etc.). Make sure you filter out the translation PRs (most of them) unless you speak the language and can review them.

Security

When there are security issues, those are handled with the highest priority. Those are normally not handled in issues and PRs but in emails, it's not public until the security disclosure is made, in most cases (always, up to now) with the version that fixes them.

Roadmap

Now, here's the current high-level tentative roadmap:

• Optional async support with AnyIO, while keeping it an optional dependency.
• Optional Pydantic support, while keeping it an optional dependency.
• Refactors and simplifications of internal code.

All this intermixed with reviews for PRs, issues, and discussions.

[johnthagen]

One limitation that I've seen come up repeatedly from friends and coworkers is T | V union syntax support. If it were at all possible to check out:

• Support for optional as UnionType (Python >= 3.10) #739
• 🐛 Fix support for UnionType with Python 3.11 #676
• Using some_type | None syntax for type annotations causes error in python 3.11 #533
• PEP 604 Support #348

I think this would remove a common stumbling block for new and seasoned users alike. ❤️

This is especially important for users of Ruff's pyupgrade rules, which will normalize Optional and Union syntax to T | V syntax automatically. Specific linter suppressions are needed to make Ruff work with Typer in this case

• https://docs.astral.sh/ruff/rules/non-pep604-annotation/

[jonaslb]

Regarding maintenance, perhaps a word of encouragement for maintainers (from you, @tiangolo) would be in order? Notably regarding the UnionType (with None) issue, @svlandeg did some great work going through all the PRs in spring and ended up recommending merging #548 to fix the issue, but deferred to you for "final decision". I don't know what the agreement is between you regarding maintenance, but it seems to me that maintainers ought to be empowered to make such merge decisions by themselves - otherwise they are hardly helping extend "merge bandwidth" (which seems to be near zero otherwise).

[tiangolo]

Thanks for the input! I recently added more info about it here. 🤓 https://typer.tiangolo.com/management/

And with the help from @svlandeg (and now also from others) we are being able to clean up more all the PRs, issues, etc. Thanks!