-
-
Notifications
You must be signed in to change notification settings - Fork 316
Nullable annotations for DSP core package, and minor refactoring #2349
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
base: master
Are you sure you want to change the base?
Conversation
…`Contains(T item)`
…h LINQ, and added nullable annotations
…notations, and a null check.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please go through again and revert nullable annotations you added to value types. since value types require nullability to be annotated explicitly, the library is already built for and tested for NVT annotations being correct.
any such changes should be explicitly justified, ideally separate from this PR, because they are behavioural changes that need to be tested and not just annotations that make users' lives easier
Summary
Added nullable annotations to class fields/properties, as well as method parameters, and minor refactorings.
Details
A majority of this PR targets the task
Nullability-annotating the librariesfrom #1580, v5 Mega-Issue. There are a few changes that target the taskCleaning up code readability, such as renaming PITA variable names to better match what they represent.Simple examples include:
pldtopayloadbgn64toreadLongMagicretto a simplified version of the type name, likewebhookormessageNotes
I tried my best to be accurate, but I may have gone overboard in some data models. Please let me know if anything marked as nullable should not be, and I'll make the necessary adjustments to the PR.