feature Add Nullable type converters #3038
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What kind of change does this PR introduce?
feature update
What is the current behaviour?
no automatic support for nullable binding converters
What is the new behaviour?
remove nullable and langversion from project files in favour of solution wide props
Add EnableNETAnalyzers and set to latest level
fix #3021
What might this PR break?
Anyone using self coded Binding converters will need to ensure they have a higher value than 10 for affinity
Please check if the PR fulfils these requirements
Other information: