add null-safety to FlxTouchManager #3440
Open
Conversation
This file contains hidden or 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
NotHyper-474
force-pushed
the
chore/touchmanager-null-safe
branch
from
fceeeb4 to
d805f5b
Compare
NotHyper-474
force-pushed
the
chore/touchmanager-null-safe
branch
from
d805f5b to
ee7ec27
Compare
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.
A contribution towards #3267, which I decided to do after getting a null reference error in a null-safe class because
getFirstwasn't annotated as nullable (although to be fair I should've read the documentation first...). I tried to do it based on how #3420 did it.Also I've noticed that PR also changes the parameter names from pascal case to camel case, should the same be done in this PR?