-
Notifications
You must be signed in to change notification settings - Fork 7
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
Cleanup utility projects #517
Cleanup utility projects #517
Conversation
9deb956
to
53f24c1
Compare
TRLevelToolset/IOLogic/IOManager.cs
Outdated
|
||
public static TR1Level? CurrentLevelAsTR1 | ||
public static TR1Level CurrentLevelAsTR1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wait, why are we removing the ?
? This function can still return null
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's currently only called in the likes of the situation below, so we still check for null at that end. I find this approach cleaner, the VS warnings when nullable
is on are less than helpful I find.
This is the UI when the level is null.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I personally think it's cleaner to leave these intact. The warnings are not wrong, even if they're annoying.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's fair. I'll re-enable and look at clearing the warnings.
I'll group projects together into separate cleanup PRs to try to keep the file numbers a bit more manageable.
This one includes the 5 utility projects - each cleanup action is in its own commit.
Part of #425.