-
-
Notifications
You must be signed in to change notification settings - Fork 171
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable nullable for Fido2.Models #466
Comments
We can't use required members yet (the net6.0 system.text.json source generator doesn't support them) -- so there's no clean way to annotate non-null members in the models library right now. We should, however, continue to annotate nullable members inside of #nullable enable blocks. If we drop net6.0 when it goes out of support, it should be trivial to annotate the remaining members. |
Yes. I guess the first step should be to have And then in a later step, the |
@iamcarbon As November 12th is coming up, marking the end of LTS .net6 - is there anything we should do here? |
I would be really helpful to annotate the nullability of the
Fido2.Models
types. In other words, to set<Nullable>enable</Nullable>
in theFido2.Models
project.This way, it would become clear for FIDO2 newbies to understand which information is optional and which one is required.
For example, in the demo, you have a line of code that stores a credential coming from
MakeNewCredentialAsync
:If both
Fido2.Models
andDemo
were NRT enabled, this would pop up as a compilation error. Righteously so, because I don't think it make sense to store a list containing anull
along the credential. So in this example, it would really help ifRegisteredPublicKeyCredential.DevicePubliKey
was declared asbyte[]?
. And I assume there's plenty more.The text was updated successfully, but these errors were encountered: