Subclassing the existing FederatedCredential forces us to make backwards compatible changes to its current deployment, which is proving to be harder than we anticipated. It was worth starting from there, but it has become clear to us that extending isn't worth the cost of making backwards incompatible changes (or a deprecation).
In this PR, we introduce a new interface type, IdentityCredential, which allows us to decouple the FedCM API from the current deployment of FederatedCredential.
Subclassing the existing FederatedCredential forces us to make backwards compatible changes to its current deployment, which is proving to be harder than we anticipated. It was worth starting from there, but it has become clear to us that extending isn't worth the cost of making backwards incompatible changes (or a deprecation).
In this PR, we introduce a new interface type, IdentityCredential, which allows us to decouple the FedCM API from the current deployment of FederatedCredential.
Preview | Diff