Repository navigation
Incorrect type returned from Users endpoint causes library to break #120
Description
Because of this change to the Users endpoint (to return multiple users when more than one user exists with the email address) the type returned by the API isn't of the correct type (currently it tries to use the User object) so the library breaks.
Metadata
Metadata
Assignees
Labels
No labels
Activity
jonbretman commentedon Nov 18, 2019
@erskingardner @jonnyom Are there any plans to make a version of this lib that is compatible with v1.4 of the API?
jonnyom commentedon Nov 20, 2019
Hey @jonbretman thanks for reaching out.
I'm afraid our contributors with Go expertise are a bit thin on the ground at the moment. Feel free to submit a PR to the SDK if you've the time though!
ruzaikr commentedon Dec 9, 2019
I'd like to try this out. Pls assign it to me :) @jonnyom
jonnyom commentedon Jan 2, 2020
Absolutely @ruzaikr ! Sorry for the delay, I've been OOO 😄 let me know if we can help 👍
catalogplus commentedon Jul 7, 2022
Hi,
I'm trying to retrieve a user with an email, but when there isn't a user with the exact email, a list is returned by the API. This causes the SDK to return an empty User struct, which is not useful.
I think the function should return a 404 error.
Thanks