CheerfulGolem

[dawn belfry]

Thanks for reporting! I will file that with the team that can fix that in the doc

[fringe dune]

e.target.value seems to still work but typescript is just complaining about it

[dawn belfry]

Interesting. So both e.value.email and e.target.value work but e.target.value gets some warning?

Would you mind sending me the warning message that you are getting so I can pass that along?

[fringe dune]

Yea so you can see in the screen shot the type that vscode infers the onChange event to be StripeLinkAuthenticationElementChangeEvent and if I look into it's type definition, it has value.email and doesn't have a target.value so based on this Typescript complains

[dawn belfry]

Perfect, thanks for the info. I will put all this in right away. Our code working is good but giving warnings/errors isn't great especially for people just starting out

[fringe dune]

Actually just a short correction, it does throw an error with e.target.value

So this is when I try to update the Email field that is created by the LinkAuthenticationElement

So if the intention for the code-example is for local react state email to be updated whenever LinkAuthenticationElement email is updated then currently it does not do so and throws this error in the browser console, and if you replace it with e.value.email it works

[dawn belfry]

Gotcha, thank you for double checking. I test this and make sure we get it sorted out in the public docs