$ the-wire ยท showcase
FASTAPI DOCS GET MULTILINGUAL OVERHAUL ACROSS FIVE LANGUAGES
By RepoJournal ยท Filed ยท About FastAPI & Pydantic ยท Composed from the cited sources ยท methodology
2 people shipped this
FastAPI's documentation pipeline shipped automated LLM-powered translation updates overnight across French, Traditional Chinese, German, Korean, and Ukrainian, signaling a shift toward continuous localization.
The FastAPI team ran an automated translation cycle that refreshed docs in five major languages [1][2][3][4][5], all generated using LLM prompts stored in the repository. This is the standard approach: changes flow through the prompt files first, then the LLMs regenerate translations, which means if your language docs feel stale, updating the corresponding llm-prompt.md file is the lever to pull. Over on the Pydantic side, a docstring fix landed for `AliasGenerator.generate_aliases()` [6] where the tuple order in the documentation didn't match what the code actually returns. The method returns `(alias, validation_alias, serialization_alias)` but the docs claimed a different order, a confusing enough mistake that someone had to file it. Nothing critical shipped, but the translation work shows FastAPI's commitment to keeping non-English docs current.
Action items
- โ If you maintain non-English FastAPI docs, review the updated llm-prompt.md files for your language fastapi/fastapi [plan]
- โ Check your Pydantic usage of AliasGenerator.generate_aliases() against the corrected tuple order pydantic/pydantic [monitor]
References
- [1] ๐ Update translations for fr (update-outdated) โ fastapi/fastapi
- [2] ๐ Update translations for zh-hant (update-outdated) โ fastapi/fastapi
- [3] ๐ Update translations for de (update-outdated) โ fastapi/fastapi
- [4] ๐ Update translations for ko (update-outdated) โ fastapi/fastapi
- [5] ๐ Update translations for uk (update-outdated) โ fastapi/fastapi
- [6] Fix tuple order in `AliasGenerator.generate_aliases()` docstring โ pydantic/pydantic
