is CredentialRepositoryV2 safe to use

[khoanguyenxuan]

Hi, we're planning to migrate to RelyingPartyV2 and CredentialRepositoryV2. We noticed CredentialRepositoryV2's methods are marked as experimental/deprecated. What is the roadmap to officially stabilize and release these classes?

Thank you.

[emlun]

Hi!

To be honest, there is no roadmap. At some point we will probably deprecate the old classes and replace them with the V2 ones in a future major release (3.0), but we have no time frame in mind at the moment. We'll probably want to resolve #289 and #393 before stabilizing the API, which may involve breaking API changes. We're keeping RelyingPartyV2 and CredentialRepositoryV2 experimental to reserve the option for such breaking API changes.

So to answer your question: the V2 API is "safe to use" in the sense that it should be equally reliable and correct as RelyingParty and CredentialRepository - they are just as thoroughly tested, for example. But they are not "safe to use" in the sense of API maturity, so if you use them you need to be prepared to adjust your code if we make breaking API changes.