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

fixed analysis issues and added support for dart 3 #93

Closed
wants to merge 5 commits into from
Closed

fixed analysis issues and added support for dart 3 #93

wants to merge 5 commits into from

Conversation

masnun-siam
Copy link

Description

Fixed the analysis issues and added support for Dart 3

...

Copy link
Owner

@ShadyBoukhary ShadyBoukhary left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you respond to the comments?
The tests are failing due to compilation errors after remove Future<>. You'll need to update the test package.

Also, why did you remove Future<>? I also see you made a lot of variables nullable. Can you explain why?

@@ -132,8 +132,8 @@ abstract class BackgroundUseCase<T, Params> extends UseCase<T, Params> {

@override
@nonVirtual
Future<Stream<T?>> buildUseCaseStream(params) =>
Future.value(Stream.value(null));
Stream<T?> buildUseCaseStream(params) =>
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why?

Function getUserOnNext;
Function getUserOnComplete;
Function getUserOnError;
Function? getUserOnNext;
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why?

@@ -26,7 +27,7 @@ class GetUserUseCase
// Trigger .onError
controller.addError(e);
}
return controller.stream;
yield* controller.stream;
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you explain the remove of Futures and replacement with this syntax?

@ShadyBoukhary
Copy link
Owner

@masnun-siam did you mean to close this? I was going to check it in after the tests pass

@masnun-siam
Copy link
Author

Sorry about not replying to the comments. Actually, it's been a while since I made the PR and when I saw your comments, I reviewed the changes I made but some of the lines didn't make sense to me either. I actually forgot why I made those changes at the first place. Also, it was one of my first PRs so I didn't check any of the tests before I made the PR so I wanted to close it and recreate it properly on my weekends if the issue still exists.

@ShadyBoukhary
Copy link
Owner

Okay, feel free to create a new one

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants