Repository navigation
🚀 Roadmap #678
Description
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.
- Pydantic support.
- Refactors and simplifications of internal code.
All this intermixed with reviews for PRs, issues, and discussions.
Activity
rafalkrupinski commentedon Feb 9, 2024
johnthagen commentedon May 2, 2024
One limitation that I've seen come up repeatedly from friends and coworkers is
T | Vunion syntax support. If it were at all possible to check out:some_type | Nonesyntax for type annotations causes error in python 3.11 #533I think this would remove a common stumbling block for new and seasoned users alike. ❤️
This is especially important for users of Ruff's
pyupgraderules, which will normalizeOptionalandUnionsyntax toT | Vsyntax automatically. Specific linter suppressions are needed to make Ruff work with Typer in this casejonaslb commentedon Jul 12, 2024
Regarding maintenance, perhaps a word of encouragement for maintainers (from you, @tiangolo) would be in order? Notably regarding the
UnionType(withNone) 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 commentedon Aug 17, 2024
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!
mrfroggg commentedon Aug 15, 2025
Hi @tiangolo !
I want to open a discussion here, I don't want to be rude about the project or your management, but I want to share:
I agree with @jonaslb on many parts.
I feel like typer is starting to look like a stalled project and I'm kind of sad about it.
Bugs (click 8.2/no_arg_is_help) now take weeks to get fixed/merged, if they are.
New features, even from reviewed PR are not merge after 8-12+ months, like new data types (JSON, bytes, Pydantic, ..)
There's a massive user base for typer, but many of us have to do a lot of gymnastic to make typer work in a more complex setup (look in the Discussions).
There's seriously good ideas and feature requests that would make typer go to the next level.
But, I think the fact that PRs are rarely merged does not incite people to contribute to typer.
So I don't know if you put this project aside, too busy in other projects or in your personal life, but, if you don't have enough time to work on this project, it would be nice if your team/maintainers could merge and manage new release to push typer to the next level and to address issues and ideas users have!
DOC: Clarify how to pass multiple values for options vs arguments (fixes