feTS roadmap

💡 This page's content and the list of tasks is synced automatically from The Guild's Notion. We are open sourcing our roadmap and tasks because we wish to build tools in the public, and allow developers to take part in the process of shaping the future of this library.
🚀 Feel free to share your thoughts, feedback and ideas with us.
👍 If you wish to show interest and help us prioritize tasks, use the 👍 on the issue.

Future

• Add feTS client to GOT Table’s repo
• create http clients benchmark
• Fix CI in Hive PRS then get another review from Hive members
• Reconsider shipping AJV & fast-json-stringify with FETS
• Support default status code for errors instead of explicit 4xx or 5xx
• HTTP Caching on server and support it with fetchache on client
• adjust flow on feTS website page
• Add links from whatwg-node repo to feTS, Yoga and other projects that rely on it
• Document how to support older specs
• Add a section in the docs about versioning
• Support application/x-www-form-urlencoded
• Support other Auth types and Security Schemes in OpenAPI operation definitions #321
• https://github.com/ardatan/feTS/pull/454/files
• Appending base path Swagger UI and console messages not up to date #164
• Make requestParams required if any param is required, otherwise keep it optional #309
• Fix allOf references #320
• feTS - Enhancing Type Safety in REST API the-guild-org/website#1297
• Support circular schema definitions #333 👀 1
• Respect security schemes #307
• Support parameters in the OpenAPI Path objects and dots in components.schemas #316