Scalar: Generate interactive API documentations from Swagger files
1–10 of 74 posts
Re: Scalar: Generate interactive API documentations from Swagger files
#2Re: Scalar: Generate interactive API documentations from Swagger files
#3Ooh this looks pretty sweet. Probably too new for me to convince my enterprise employer but will keep an eye on this for sure.
Re: Scalar: Generate interactive API documentations from Swagger files
#4Re: Scalar: Generate interactive API documentations from Swagger files
#5edit: why downvotes?
Re: Scalar: Generate interactive API documentations from Swagger files
#6Why did you decide to open-source it? How will you make money? edit: why downvotes?
Re: Scalar: Generate interactive API documentations from Swagger files
#7Aren't Redocly and Swagger UI open-source too?
Re: Scalar: Generate interactive API documentations from Swagger files
#8I like my API documentation to mainly be boring old static HTML, with any interactive features using JavaScript layered over the top.
Using HTML makes it faster to load, easier to get it indexed by search engines, easier to save and run offline and easier to process through LLM tools like ChatGPT and Claude.
Re: Scalar: Generate interactive API documentations from Swagger files
#9Looks very JavaScripty. I like my API documentation to mainly be boring old static HTML, with any interactive features using JavaScript layered over the top. Using HTML makes it faster to load, easier to get it indexed by search engines, easier to save and run offline and easier to process through LLM tools like ChatGPT and Claude.
This is definitely a more Javascript heavy approach but without JS you can't get some nice quality of life features like the embedded REST API client for experimenting with endpoints.
As for LLMs we have had the best experience passing them Swagger files directly and not relying on an intermediate parse to text.
Re: Scalar: Generate interactive API documentations from Swagger files
#10Operation.summary is typically derived from the documentation for an API operation, and should not be used as the operation title as it is far too long. Instead use the operationId and path.
I can't get it to render schemas for a bunch of my OpenAPI documents, and there are no error messages to guide me. Does this handle recursive schemas (which can never be fully expanded)?