Closed hanspagel closed 2 weeks ago
Latest commit: 5c955c8a73011a9377b40b2da1ff61e51a720ce4
The changes in this PR will be included in the next version bump.
Not sure what this means? Click here to learn what changesets are.
Click here if you're a maintainer who wants to add another changeset to this PR
5c955c8(current) vs aec9f22 main#137(baseline)
no changes
no changes
Bundle analysis reportβBranch feat/new-types-packageβProject dashboard
Generated by RelativeCIβDocumentationβReport issue
Latest commit: |
5c955c8
|
Status: | β Deploy successful! |
Preview URL: | https://c3e716fd.openapi-parser.pages.dev |
Branch Preview URL: | https://feat-new-types-package.openapi-parser.pages.dev |
hey @hanspagel we are going to move the types into the monorepo so I'll copy them over, then there should be no breaking changes here. We can also just re-export them after for a single source of truth
We modified and extended the
openapi-types
package for our use case. Weβre basically allowing any user input, but still maintaining the types based on the OpenAPI specification.With this PR, weβre exposing those types as a separate, dependency-free package called
@scalar/openapi-types
. Even comes with basic type tests. :)Note: This is a breaking change. Instead of importing types from
@scalar/openapi-parser
, users now have to import from@scalar/openapi-types
.Usage
And use it like this: