[melolife]

I'm interested in new offerings in this area, as all of the existing options are pretty janky. A couple of thoughts:

Operation.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)?

[cameronrohani]

This is great feedback that we'd love to take a closer look at.

If you have a chance please reach out to [e-mail] and we can start working on some improvements.

[melolife]

After some more experimentation it looks like you don't support allOf/anyOf/oneOf which seems like a pretty big hole.

[marclave]

our swagger parser isnt perfect yet, appreciate this comment and I added it to triage. We will get this fixed quick

[jamietanna]

Swagger or OpenAPI parser?

[marclave]

Swagger + OpenAPI v3/v3.1 parser, sorry I needed more coffee was up way too late this week with launch

Will update the README to make this more clear

[marclave]

hey! co-founder here, appreciate your comment.

Ah that's great feedback!

As for the rendering of the schemas, we have a pull request in draft from this morning! hopefully will be done ASAP

https://github.com/scalar/scalar/pull/244

[epse]

I thought most of the alternatives used summary as a title and description as a body, which is how we've been writing it as well? Or am I out of wack here?