Part of umbrella issue #16. Should be able to be started at any time.
Problem
In order to maximize compatibility with the main Coder API types, we should rip out our current type validation setup and custom type definitions, and defer to the types defined via the Coder types NPM package. Normally this wouldn't be all that safe, but because we own both packages, there shouldn't be any issues around this, and the migration will remove some runtime overhead.
Desired outcome
Import the Coder type definitions via NPM, and make them a package.json dependency
Update all existing type references in the codebase to use the new type definitions
Rip out Valibot logic for parsing API responses (Valibot should still be kept for parsing YAML config files)
Update all mock data to reflect the new type definitions (might be able to copy-paste from the main Coder repo)
Part of umbrella issue #16. Should be able to be started at any time.
Problem
In order to maximize compatibility with the main Coder API types, we should rip out our current type validation setup and custom type definitions, and defer to the types defined via the Coder types NPM package. Normally this wouldn't be all that safe, but because we own both packages, there shouldn't be any issues around this, and the migration will remove some runtime overhead.
Desired outcome
package.json
dependency