Nullable #365
Merged
Nullable #365
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…cationsController. However the code in save-point/09 and instructions were not updated. This fixes the issue.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR is to address the lack of Nullable context in the workshop. Fixes issue #105
Nullable context was enabled on all projects: Client, Server, Shared, Component Libs.
Nullable was used in an unopinionated way through the examples. Only the minimum required changes were made to the codebase to ensure the focus of the demo was Blazor and not "nullable patterns".
EditorRequiredwas also added to some parameters to help enforce nullable concerns, although this isn't a bulletproof solution.Some additional issues were resolved:
Fixes issue #358 , Fixes issue #238 (related)
Fixes issue #364
Fixes issue #344