Skip to content

Conversation

Jack251970
Copy link
Member

Enable nullable for enum localize classes

Follow on with #38.

#38 introduces INotifyPropertyChanged which contains nullable type ? usage. So we should enable nullable for enum localize classes. Or it will lead to VS build warning:

Screenshot 2025-08-13 104035

Bump version to v0.0.5

Version bump for test release.

Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This PR enables nullable reference types for enum localize classes and bumps the package version to 0.0.5. The changes address build warnings that occur when nullable reference types are used with INotifyPropertyChanged from a previous PR (#38).

  • Enable nullable reference types in generated enum localize classes
  • Update version numbers from 0.0.4 to 0.0.5 across all version properties

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.

File Description
Flow.Launcher.Localization.csproj Version bump to 0.0.5 for package release
EnumSourceGenerator.cs Enable nullable context and add nullable annotations to string properties

Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.

@VictoriousRaptor
Copy link
Contributor

Not quite familiar with this part. Is it good to go?

@Jack251970
Copy link
Member Author

Not quite familiar with this part. Is it good to go?

I think so. It will not change any runtime behaviour and is just used to resolve compile warnings.

@Jack251970 Jack251970 merged commit d022ba5 into main Aug 18, 2025
4 checks passed
@Jack251970 Jack251970 deleted the enum_nullable branch August 18, 2025 03:15
@jjw24 jjw24 added the bug Something isn't working label Aug 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants