refactor: improve CLI type safety and log level consistency #565
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.
The CLI unnecessarily ignored some of the typescript SDK's types, which made it less type-safe and harder to maintain. The log levels were also hardcoded as strings instead of pulled from the types exposed by the SDK, which caused log levels to be inconsistent across the codebase.
Motivation and Context
I was working on a PR for a new CLI feature and noticed that a lot of the types were "any", which was a smell to me knowing that the typescript SDK uses strong typing. Instead of including this refactor in that PR, I thought it would be better to pull it out as a standalone PR.
How Has This Been Tested?
Tested locally using the CLI against my local MCP server, and all linting/testing run for the repo.
Breaking Changes
No, it should not affect anyone.
Types of changes
Checklist
Additional context
None.