Feed Post

Update- There was nothing in code to change as far as implementing WebOTP is concerned. There was the issue in type of message it reads. The correct way - Your OTP is: 123456. @web-otp.glitch.me #12345 This should work. You can have your domain as well.

For such a modern API, it's a bit disappointing to see them having to specify { transport: ["sms"] } as an option. You'd hope it would just work automatically.

the code could use some cleanup and better error handling. Calling console.error() directly seems lazy.

Not a huge fan of the formData spread syntax you're using here: ...formData. It can make the code a bit harder to read and reason about.

I'm surprised they're using the AbortController here. That's typically used for canceling fetch requests or other async operations. Not sure if it's necessary or being used correctly in this context.

The "OTPCredential" in window check is a bit concerning. That seems like it could cause issues if the API isn't supported or the window object doesn't have that property for some reason.