-
Notifications
You must be signed in to change notification settings - Fork 199
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
Nullsafety #586
Nullsafety #586
Conversation
added linter exceptions for string single quotes and pedantic local variable type rule
additional fixes
Lib:: enchanced error handling, refined nullability on certain types
…stic POD so should be ignored when checking for equallity
…nd type annotations
…lue; made fields final
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.
Just some early feedback as I'm on 11/51 files - I'll finish it tomorrow. Looks nice so far, thanks for the PR!
xcode noise
* Add bluetooth-central key to README.md Based on dotintent#530 * Update README.md
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.
Got a few questions and a change request, but other than that looks OK!
added final qualifiers isConnectable is back to nullable since it's only available on iOS on android it will be null which does not mean false!!
_parseCharacteristicWithValueWithTransactionIdResponse():: signature is now type safe moved the rawJsonValue String checking to the caller side
@mikolak I don't know how to fix this one mate. |
Yeah, it's because it's a PR from a fork instead of a MR from this repo - don't mind. |
also _resetScanEvents introduced to null the underlying scream out
…g even if withResponse is false additional type safety on invokeMethod calls
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 appreciate your work, but please, revert the last commit. Native client has to either return characteristic or error and I'd rather have a null pointer exception thrown than some custom exception that does not give the API consumer any insight or returning an invalid default value.
There's a bug where the response is not properly returned on Android, but it's a multilayer issue that originates in Android's MBA, any changes to interface will be done along with fixing it.
Changes to the mixins are unrelated to this PR and should be in a separate PR.
Summing up: thanks for all the work on null safety! ❤️ Please, run the formatter in scanning_mixin.dart and revert commit 86dafd6
(Characteristic:: refactor on Futures to always complete...
) and I'll merge it! 🙂
…something even if withResponse is false" This reverts commit 86dafd6.
# Conflicts: # lib/src/bridge/lib_core.dart
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.
A few minors, but I'll take care of those myself. Thank you very much for the PR!
Hey, guys! I've made a lot of effort to port the dart codebase to a nullsafe environment. I would appreciate someone taking a look at it.
known issues:
-not all of the test are compiling, although I've tried to make it work I've even ported some of the mocks to the new generated mocking scheme. FIXME: I think many of the test should be retired, in favour of general nullsafety. Please help me on that.
-there was a bleadapter lifecycle fiasco, because the DevicesBloc destroyed the client on dispose(), making the internal adapter unreachable, after going to detail view. Although I have attempted to fix this by just removing the destroy client call from DevicesBloc.dispose() but I'm just not certain this was the right solution in terms of good design.
Thanks for taking the time!
Fixes #556