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

BaseActivity.Current should be nullable #18573

Open
morning4coffe-dev opened this issue Oct 24, 2024 · 0 comments · May be fixed by #18582
Open

BaseActivity.Current should be nullable #18573

morning4coffe-dev opened this issue Oct 24, 2024 · 0 comments · May be fixed by #18582
Assignees
Labels
kind/enhancement New feature or request

Comments

@morning4coffe-dev
Copy link
Member

The BaseActivity.Current is defined as a non-nullable property, but in certain scenarios, such as when the app is in the background, it returns null.

Why is the return value marked as non-nullable when it can potentially return null in these cases? Shouldn't this property be marked as nullable to prevent potential crashes?

Originally posted by @EricKwon94 in #18566

@morning4coffe-dev morning4coffe-dev self-assigned this Oct 24, 2024
@morning4coffe-dev morning4coffe-dev added the kind/enhancement New feature or request label Oct 24, 2024
@morning4coffe-dev morning4coffe-dev linked a pull request Oct 25, 2024 that will close this issue
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant