Refresh TypeScript Desktop API SDK from current spec - #45
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 published TypeScript SDK didn't expose parts of the API that Desktop already serves. In the v5 tag,
src/resources/index.tshas no app setup, bridge login, or label exports. Compare that withapi.md:100-102,:174, and:240-244in this PR: those are the routes developers needed but couldn't call through the SDK.I regenerated the client from the current Desktop API spec instead of adding those methods by hand. That gives the new routes and response models the same shape as the server. I kept the MCP package and the existing request-body fix in place so refreshing the SDK wouldn't drop either one. This PR updates
next; v6.0.0 is the published release with the migration details.Tag
@indentto continue the conversation here.