maintenance: migrating code base to null-safety about flood_mobile

[mail-man26]

@mail-man26 I have assigned this issue to you.

Thanks for assigning!! I am working on it

[pratikbaid3]

@prajwal27 you can comment out the local package usage for now and use the one on pub.dev. That was done to make quick changes in the package itself. The package on pub.dev would be at par with the local package for the most part so it shouldn't cause any issues. If it is does, feel free to open an issue on https://github.com/pratikbaid3/flutter_client_sse.

[mail-man26]

I would like to work on this issue

[pratikbaid3]

@mail-man26 I have assigned this issue to you.

[pratikbaid3]

@mail-man26 are you still working on this issue?

[prajwal27]

@pratikbaid3 can I work on it this time?

[pratikbaid3]

@prajwal27 Sure, I don't think @mail-man26 is working on it. I'll assign it to you.

[prajwal27]

@pratikbaid3 the contributing guidelines are absent. Should I fork this repo and make a PR or should I create a branch and make PR?

[pratikbaid3]

@prajwal27 please refer to CONTRIBUTING.md(https://github.com/CCExtractor/Flood_Mobile/blob/master/CONTRIBUTING.md). You can use the develop branch to create a fork and then make a PR.

[prajwal27]

@pratikbaid3 , the project is using another local package flutter_client_sse, that probably needs to be migrated first,
or
Shall I discard the local usage of the package and use this directly https://pub.dev/packages/flutter_client_sse ?

[pratikbaid3]

Resolved in #22