I had to revisit how I tried to teach TypeScript about "cable" authenticator transport in #198. This time I followed the "Future" pattern I established with AuthenticatorAttestationResponseFuture and defined two new types:
AuthenticatorTransportFuture
PublicKeyCredentialDescriptorFuture
These new values replace similarly named types referenced out of TypeScript's DOM lib, including in generateRegistrationOptions() and generateAuthenticationOptions() so these'll stop erroring out on code that is otherwise fine pre-5.2.0
This should allow me to continue adapting to changes to WebAuthn faster than TypeScript's DOM lib is able to while also making it straight-forward to remove these "Future" types for their contemporary counterparts when the DOM lib gets updated.
I had to revisit how I tried to teach TypeScript about
"cable"authenticator transport in #198. This time I followed the "Future" pattern I established withAuthenticatorAttestationResponseFutureand defined two new types:AuthenticatorTransportFuturePublicKeyCredentialDescriptorFutureThese new values replace similarly named types referenced out of TypeScript's DOM lib, including in
generateRegistrationOptions()andgenerateAuthenticationOptions()so these'll stop erroring out on code that is otherwise fine pre-5.2.0This should allow me to continue adapting to changes to WebAuthn faster than TypeScript's DOM lib is able to while also making it straight-forward to remove these "Future" types for their contemporary counterparts when the DOM lib gets updated.