fix: prevent duplicated schema types by using JSON schema throughout #253
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.
Reviewer: @GioSensation
Asana:
Description
The main entry point for defining API calls is now expressed in JSON schema for consistency. This has the nice side-effect of solving the 'duplicated types' problem described in the tasks above because we are no longer building the schema up ourselves in the JS.
Steps to test
If TS + integration tests pass, then we're all good here :)