Skip to content

Enable Nullable #2282

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

Merged
merged 7 commits into from
Dec 15, 2022
Merged

Enable Nullable #2282

merged 7 commits into from
Dec 15, 2022

Conversation

stefannikolei
Copy link
Contributor

@stefannikolei stefannikolei commented Oct 30, 2022

Prerequisites

  • I have written a descriptive pull-request title
  • I have verified that there are no overlapping pull-requests open
  • I have verified that I am following the existing coding patterns and practice as demonstrated in the repository. These follow strict Stylecop rules 👮.
  • I have provided test coverage for my change (where applicable)

Description

Enabled nullable analysis.
Disabled in all files where errors happened.

First step of #2231

* Disable nullable for all files with #nullable disable

Replace order of header and annotation

Only use nullable disable in files with errors
@JimBobSquarePants
Copy link
Member

Wow! Please tell me you did some sort of find/replace for this?

@stefannikolei
Copy link
Contributor Author

Wow! Please tell me you did some sort of find/replace for this?

Adding it in all files works by find and replace.
Adding it only to files which had errors enforced me to use a good bottle of wine 😅

@@ -57,7 +57,7 @@ public override void ToAbgr32(Configuration configuration, ReadOnlySpan<Abgr32>
{
Vector4Converters.RgbaCompatible.ToVector4(configuration, this, sourcePixels, destVectors, modifiers.Remove(PixelConversionModifiers.Scale));
}

Copy link
Member

Choose a reason for hiding this comment

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

Any idea what caused these changes?

We should probably add #nullable disable to all T4 templates at some point.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

No clue. I reverted a bunch of changes. Probably overlooked this one.

I can only imagine that opening the file in rider on Mac caused this.

Copy link
Member

@JimBobSquarePants JimBobSquarePants left a comment

Choose a reason for hiding this comment

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

This looks good to me. Thanks!

@JimBobSquarePants
Copy link
Member

I broke your PR. Sorry!

@stefannikolei
Copy link
Contributor Author

I broke your PR. Sorry!

I fixed it. One build step is failing. I am not able to trigger it. For me the error seems unrelated. @JimBobSquarePants Could you have a look please?

@stefannikolei
Copy link
Contributor Author

@JimBobSquarePants Is there anything blocking this pr? Anything I can do? Or you just waiting for a good "moment" to merge?

@JimBobSquarePants
Copy link
Member

Sorry for the delay. Yep everything looks good. Just trying to get #2276 in first as it will be easier to merge this one after than the other way round.

@stefannikolei
Copy link
Contributor Author

@JimBobSquarePants I added another nullable disable. So I should be finished now

Copy link
Member

@JimBobSquarePants JimBobSquarePants left a comment

Choose a reason for hiding this comment

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

Awesome! Thanks very much for doing this. I appreciate that it's a chore!

@JimBobSquarePants JimBobSquarePants merged commit 0328475 into SixLabors:main Dec 15, 2022
@stefannikolei stefannikolei deleted the stefannikolei/add-nullable-annotation branch January 1, 2023 10:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants