Revert prerequisiteTreeSchema to what it was originally. Also, override the OpenAPI metadata on it so it doesn't cause any errors, and set the metadata properly so consumers can receive the correct type data.
Honestly this was a lot less involved than I expected.
Related Issue
Closes #28.
Motivation and Context
Now we won't have to hardcode the prereq tree type in the API's consumers.
Paste the following snippet into another TS file and play around with it, ensuring that the PrerequisiteTree type behaves as expected.
// assuming the output is named "anteater-api-types.ts"
import { components } from "./anteater-api-types";
type PrerequisiteTree = components["schemas"]["prereqTree"];
## Types of changes
<!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
- [x] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to change)
## Checklist:
<!--- Go over all the following points, and put an `x` in all the boxes that apply. -->
<!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
- [ ] My code involves a change to the database schema.
- [ ] My code requires a change to the documentation.
Description
Revert
prerequisiteTreeSchemato what it was originally. Also, override the OpenAPI metadata on it so it doesn't cause any errors, and set the metadata properly so consumers can receive the correct type data.Honestly this was a lot less involved than I expected.
Related Issue
Closes #28.
Motivation and Context
Now we won't have to hardcode the prereq tree type in the API's consumers.
How Has This Been Tested?
openapi-typescriptto generate a types file from the dev server.PrerequisiteTreetype behaves as expected.type PrerequisiteTree = components["schemas"]["prereqTree"];