Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Suggestion: Following nullable reference types
See original GitHub issueI’ve come to realize that I’m now basically putting [NotNull] everywhere.
Maybe you’ve heard about the proposal for nullable reference types that will make unqualified reference types be non-nullable by default. (champion)
Not sure how likely that is to make it, but it’s one of the more popular proposals.
I think for NSwag, it makes sense to have a mode where the [NotNull] is implicit on everything: Properties, return values and parameters - and then have another attribute [Null] or [CanBeNull].
Issue Analytics
- State:
- Created 6 years ago
- Reactions:1
- Comments:9 (6 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
The attributes are also defined in https://www.nuget.org/packages/ReSharper.Annotations/
The attributes in NJS are also allowed for the return type, eg.:
CanBeNullAttribute, but its not yet in NJsonSchema.Annotations (you have to implement it yourself). Ill add it just now…