Replies: 5 comments
|
Hi @misuvii - thanks for raising this
Could you share the code that raises the error? (and a link to the documentation) |
|
@adamjmcgrath This is the code that raises the error |
|
Thanks for clarifying @misuvii - I've raised this with the team that owns those endpoints, will see if we can get this changed. In the meantime, you can safely cast the const linkUsersTask = async () => {
await client.users.link(
{ id: primary.user_id! },
{
user_id: secondary.user_id!,
provider: identity.provider as PostIdentitiesRequestProviderEnum,
}
);
}; |
|
Also hit this issue today, will use typecasting to bypass for now |
|
Thanks for the report! Apologies for the delay in following up on this. We'd recommend upgrading to v5(if you haven't already) as v4 is no longer actively maintained; see the v5 Migration Guide to get started. I'll be moving this to discussion to decide a way forward wrt v4. Please reopen or file a new issue if you continue to see this problem on v5. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Checklist
Description
The field
provideris defined asstringin the interfacesUserIdentitiesandGetUsers200ResponseOneOfInnerIdentitiesInner. But for the methodlinkinuserssection of the management api client, the optional fieldproviderin the bodyParameters of typePostIdentitiesRequestis defined asPostIdentitiesRequestProviderEnum. Due to this, one can't simply extract identitites from a user profile and loop it to link as suggested in the documentation, Since it throws a type mismatch error forprovider.Reproduction
The scenario is finding every account with same email id and linking it together.
Additional context
No response
node-auth0 version
4.0.1
Node.js version
18
All reactions