-
Notifications
You must be signed in to change notification settings - Fork 217
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
Parse tspconfig as yaml to be able to figure out where errors are #2273
Parse tspconfig as yaml to be able to figure out where errors are #2273
Conversation
Changes in this PR will be published to the following url to try(check status of TypeSpec Pull Request Try It pipeline for publish status): Website: https://cadlwebsite.z1.web.core.windows.net/prs/2273/ |
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.
Would also be nice to see the impact on typespec-azure
packages/samples/test/output/grpc-kiosk-example/@typespec/openapi3/openapi.yaml
Show resolved
Hide resolved
packages/samples/test/output/grpc-library-example/@typespec/openapi3/openapi.yaml
Outdated
Show resolved
Hide resolved
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.
Please file an uptake PR in Azure/typespec-azure before merging.
PR https://github.com/Azure/typespec-azure/pull/3513 |
fix #2298
Update yaml parser library from
js-yaml
toyaml
which allow us to have an ast and resolve where values are coming from.Before
Now:On top of providing error locations for config errors that the compiler can resolve this also setup the base to provide the ability for an emitter to report na error on its emitter options and show where it is.