test: exercise apiKeys.get in SDK parity harness#38
Merged
Conversation
The apiKeys.get method shipped in #36 but the parity harness runner (test/run-sdk.mjs) had no dispatch case for it, so the monorepo harness-completeness check flagged sdk-js as not covering api-keys.get. Wire the op through to client.apiKeys.get. Co-authored-by: Cursor <cursoragent@cursor.com>
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.
Summary
api-keys.getthrough the parity harness runner (test/run-sdk.mjs) toclient.apiKeys.get(rest[0]).Why
apiKeys.getshipped in #36, but the harness runner had no dispatch case, so the monorepo harness-completeness check flagged sdk-js as not coveringapi-keys.get. This closes the gap so parity goes green without a temporary exclusion.Test plan
node --check test/run-sdk.mjsMade with Cursor