Swagger

Raised as a usability problem by 12 people on Hacker News over 10 years (2017–2026), in 8 threads.

People raised many different problems with Swagger, but no single problem has yet been raised by 3 people in 3 different months and threads.

Unreviewed issues were grouped by machine: Claude Haiku labelled each comment as a usability complaint, named what it's about and summed up the problem in a line, and a small model grouped similar problems. Nobody has checked them by hand. Expect mistakes.

The newest 13 complaints

Must open each endpoint one by one to check if it is protected2026-04-16
Hard to navigate the React source code and find how to customize it2022-08-10
Large nested responses with many fields become an unreadable mess2020-10-23
V3 rewrite in React made it too hard to find and change code2020-07-14
Markdown fields render inconsistently, and some show as plain text with newlines lost2019-10-18
Error messages are hard to understand when writing specs2017-10-24
Took more time to write the spec and get the UI behaving than the API itself2017-04-04
Writing the Swagger spec and getting the UI to behave takes far too long2017-04-04
Writing a Swagger file is harder than writing the API itself2017-04-04
Editor marks everything red for no apparent reason, inconsistently2017-04-04
Swagger UI project is very slow to interact with2017-03-22
No file dialog to load and save files, which is annoying2017-03-22
Endpoints must be clicked open one by one, and models need arrow-by-arrow expansion2017-03-22