Add ability to check Fern Definition against OpenAPI spec

[zachkirsch]

How important is this?

P0 - Critical (Blocking work)

What's the feature?

We currently generate an openapi spec for our docs (and hopefully one day - SDKs!) using tsoa.

However, when it comes to ordering of properties, documenting fields, etc. tsoa is great, and I'd rather just use the fern definition.

Of course, I don't want by backend to drift from my openapi spec.

I think the ideal solution is to:

1. Manually maintain a fern definition for my public API
2. continue generating an openapi spec using tsoa
3. Add some CI-time check that ensures that my fern definition does not drift from my openapi spec

Of course, I could do this manually, but I think it would be awesome if fern supported this out-of-the-box!

Anything else? (Optional)

I would be down to contribute but would need some handholding

Are you interested in contributing this feature?

Yes

[dsinghvi]

@zachkirsch want to grab some time to chat through how you could buld this? https://calendly.com/deep-singhvi/15min