Refactor code to use Provider Architecture - Githubissues

CodeFlowOrg / forestTreesTagging

This project has the vision to assist the officials for Forest trees census and tagging each tree with proper location (latitude and longitude), tree type, and other arguments. and further had the plan to apply data analysis over-collected data.

20 stars 38 forks source link

Refactor code to use Provider Architecture #80

Open Sameerkash opened 3 years ago

Sameerkash commented 3 years ago

Feature request:

On the course the current code is headed, it can get really messy to manage state and other code. It'd be best if architecture is implemented when the code hasn't grown too much yet.

I'd like to propose using the Provider package with ChangeNotifier as this is beginner-friendly and least complex to implement.

The Tasks of this issue would be

Adding provider package and creating a MultiProvider using ChangeNotifier for any state.
Create a ChangeNotifier for handling Authentication and move auth logic into that.

Since we'll be having multiple services as this app demands so, we will use getIt package for easy singleton access across the app.

Refactor any service class to use GetIt.

This issue can of course be split up as it'll be a lot of code refactoring to be done by two people

Mohitmadhav commented 3 years ago

Can we use Bloc state management @Sameerkash?

Sameerkash commented 3 years ago

@Mohitmadhav I think Bloc would make it necessarily complicated. Provider would be preferred.

Priyanshu078 commented 2 years ago

Can I work on this issue? I can solve this issue using provider

Priyanshu078 commented 2 years ago

@Sameerkash

Runner-Shane commented 2 years ago

Hi, is there anyone working on this issue? if not then can I work on this.