-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: support typespec as an input format #158
Conversation
@@ -24,8 +24,18 @@ | |||
"test": "jest" | |||
}, | |||
"devDependencies": { | |||
"@azure-tools/typespec-autorest": "^0.41.1", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These are just required by the integration tests, hence not included in peerDependencies
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Split from packages/openapi-code-generator/src/core/file-loader.ts
- not actually changed, aside from using json5
for parsing json
input
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Split from packages/openapi-code-generator/src/core/file-loader.ts
- not actually changed
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is the meat of the implementation
adds https://typespec.io/ as a supported input format, using it's typespec -> openapi3 conversion package.
--input-type=[openapi3|typespec]
, defaulting toopenapi3
peerDependencies
, eg:also finally got sick of
xargs
requiring a255
exit code to halt on failure, and switched the integration test generation scripts over to node, which also prefixes the output to make it easier to follow.resolves #148