-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Test other auth methods against fake-seam-connect #150
base: main
Are you sure you want to change the base?
Conversation
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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. |
c317bd7
to
2810f4e
Compare
Trying to use the changes introduced in seamapi/fake-seam-connect#200 (comment)