feat(type-safe-api): support for modelling apis in typespec #874
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds support for modelling both REST and WebSocket APIs in TypeSpec: https://typespec.io/
Similar to Smithy, TypeSpec provides a nice abstraction for modelling API operations and their inputs and outputs. TypeSpec syntax takes some inspiration from TypeScript, and so may be more intuitive for some users. TypeSpec operates in the Node ecosystem, and so no additional global dependencies are required for its use (unlike Smithy which requires Java and Maven).