Don't use classes from Development-namespace in examples

[hbjoroy]

Thank you for releasing v4.0.0 - the beta has been great for learning and experimenting with Passkey.

I'm at the moment experimenting with 4.0.0 - and got stuck in the demo, since Fido2NetLib.Development is being used in the demo and the REAME.md (StoredCredential).

Either StoredCredential should be included in some helper-namespace (or even helper package) or the demo should declare the class in the demo, the demo should be runnable with the fido2 nuget package. We are of course able to hunt it down on github, but at the very least README.md shouldn't assume you do that.

[abergs]

@hbjoroy We expect every consumer to implement their own version of a stored credential that integrates with their existing domain and storage layer. That is why we never package and distribute our implementation.

The Fido2 library outputs a RegisteredPublicKeyCredential which you should map to whatever poco/domain objects you want to store.

The reason it's not in included in Demo project is because it's also used in other demoes, like the Blazor one and we'd prefer to keep it simple for ourself when it comes to maintenance.

However, we could better document that we expect you to use your own poco and that there is nothing magical about StoredCredential.

[hbjoroy]

Yes, I understand. I would like to see a demo using the nuget package - not the source tree, but I respect that you have made these decicions.

I'll be able to figure it out. To make it harder on myself I try to use the package with F#, also I try to implement the client from scratch using typescript/Vue (which I am no expert at). Also for my experiment I use ComosDb with CosmosDB Sql interface, so the EF-things are also a bit alien to me (left EF some twelve years ago... understand it is better these days).

I guess making it more clear in the README that StoredCredential and the strategies for storing data must be provided by your own code would have saved me some time.

Thank you for your reply!