Skip to content
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

Remove Unsupported "!!" null-checking syntax from BlazorWebView #7484

Merged
merged 2 commits into from
May 25, 2022

Conversation

drasticactions
Copy link
Contributor

The !! syntax was used in the C# 11 previews and will be removed from the final release.(https://devblogs.microsoft.com/dotnet/csharp-11-preview-updates/#remove-parameter-null-checking-from-c-11). With that in mind, we should remove use of it from our repo.

AFAIK it was only used in the Blazor codebase. This PR should remove it and replace it with supported null checks.

@drasticactions drasticactions requested a review from a team as a code owner May 25, 2022 22:04
Copy link
Contributor

@TanayParikh TanayParikh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@TanayParikh TanayParikh enabled auto-merge (squash) May 25, 2022 22:10
@Eilon Eilon added the area-blazor Blazor Hybrid / Desktop, BlazorWebView label May 25, 2022
Copy link
Member

@Eilon Eilon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So!! sad!!

Co-authored-by: Eilon Lipton <Eilon@users.noreply.github.com>
@TanayParikh TanayParikh merged commit d6bc1ca into dotnet:main May 25, 2022
@drasticactions drasticactions deleted the dev/timill/blazor-csharp branch May 26, 2022 03:08
@github-actions github-actions bot locked and limited conversation to collaborators Dec 21, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-blazor Blazor Hybrid / Desktop, BlazorWebView
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants