Null safety

[naamapps]

Null safety

[naamapps]

@BirjuVachhani
I think the last one doesn't show an error because the extension is on Iterable? while the others are part of the Dart language and it is not an extension.
I think this is also the case with strings but i'm not sure.

[BirjuVachhani]

@naamapps I have added these extensions back for now.

dependencies:
  screwdriver: ^2.1.0

[naamapps]

@BirjuVachhani Thank you, much appreciated!

[BirjuVachhani]

@naamapps I am working it. Will publish it soon.

[BirjuVachhani]

@naamapps

Null-safe version has been released. Please check CHANGELOG before upgrading.
https://pub.dev/packages/screwdriver

[naamapps]

Hi, thanks for the update.
Why did you remove the extensions Iterable.isNullOrEmpty, Iterable.isNotNullOrEmpty, String.isNullOrEmpty, String.isNotNullOrEmpty, String.isNullOrBlank ,String.isNotNullOrBlank?
Even when there is null safety it is still required to do null checks..

for the collections it can be done like so:

extension NullableIterableScrewDriver<E> on Iterable<E>? {
  bool get isNullOrEmpty => this == null || this!.isEmpty;
  bool get isNotNullOrEmpty => this != null && this!.isNotEmpty;
}

What do you think about adding new extensions only for nullable collections or strings?

[BirjuVachhani]

@naamapps

String? testing;
testing.substring(5); // This shows error

List<int>? list2;
print(list2.first); // This also shows error

List<int>? list3;
print(list3.isNullOrEmpty); // But this doesn't :(

I thought it would show error when accessing nullable types and we would need to use ? for null safety but now it seems that extensions doesn't respect whether the receiver is null or not.

Seems that I need to add those extensions back but for Iterable? type.