FilledStacks / FilledStacks/provider_architecture
Caching the Model Data
Nobody has claimed this yet.
- Dominant language
- Dart
- Stars
- 86
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Description
First of all thanks for provider_architecture in reducing the pain of building up a large and maintainable app
After reading couple of issues and blog posts. Registering viewModel as registerLazySingleton rather than registerFactory to avoid multiple requests in API or any data layer.
I want to know how to achieve caching in this architecture?
- One way I could think of handling in
Serviceswhich would give cached data and making background call to update the new data.
But I am interested in your view and how do you approach it. It would be nice if you are able to explain it with a real use case.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by reviewing the provider_architecture guidance around registerLazySingleton, registerFactory, services, and viewModels, then clarify whether the desired outcome is documentation or an example. Done means the caching approach and a real use case are documented clearly enough for users to follow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dart
- Domain
- data
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100