Test other auth methods against fake-seam-connect #150
+321
−197
Conversation
This file contains 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
razor-x
commented
Aug 5, 2024
| const devices = await seam.devices.list() | ||
| t.true(devices.length > 0) | ||
|
|
||
| const seamUsingApiKey = SeamHttp.fromApiKey(seed.seam_apikey2_token, { |
There was a problem hiding this comment.
seam_apikey2_token or seam_apikey1_token?
|
@andrii-balitskyi This is low priority, but if you feel like working out this puzzle, it would be nice to find the bug in fake-seam-connect and get the tests passing. Basically, this PR was merged, but something is not implemented right there: seamapi/fake-seam-connect#200 (comment) A good start would be adding a test to fake-seam-connect that reproduced the errors in this PR. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Trying to use the changes introduced in seamapi/fake-seam-connect#200 (comment)