Comments (2)
Circular dependencies are not allowed for performance and simplicity reasons – on the top of the maintainability bonuses.
As such, they will never be allowed.
But there should be an alternative solution for your case. For example, you could have:
hide
/ \
comments posts
\ /
messages
It's hard to say without knowing exactly what you want. But in any case, circular dependencies are not the solution
Feel free to share about your use-case so that I can help you with it.
from riverpod.
Thanks Remi! Sorry that your comment slipped through the cracks. Appreciate the help!
I didn't quite get your example. I went back to the project and split up Repository
which had one responsibility too many. Cyclic deps gone.
Fwiw I found ref.read
a bit confusing when passing it around/working with many dependencies (esp since read
is used throughout rp in different contexts). I started being more specific with refs and used an alias, i.e. repositoryRef.readDependency(x)
from riverpod.
Related Issues (20)
- [riverpod_lint] avoid_manual_providers_as_generated_provider_dependency HOT 2
- ref.refresh() fails when the returned value of a FutureProvider is an empty list HOT 1
- ref.invalidate() does not make another request to the server HOT 1
- update the TODO example. HOT 3
- The `API Reference` link in the sidebar leads to `hooks_riverpod` api reference HOT 1
- AsyncValue Issue HOT 3
- Stream ending with BadState when navigating back and forth quickly HOT 8
- Bad state: called ProviderSubscription.read on a subscription that was closed HOT 5
- Generics in Notifier generated HOT 2
- Support ProviderSubscription read inside useEffect dispose.
- Experimentation with macros
- [quality of life] make `riverpod_annotation` re-export utilities such as `@protected` HOT 2
- autoDispose is not working when the widget is disposed,and the same widget is registered again after the previous widget was disposed HOT 8
- `Unhandled Exception: setState() or markNeedsBuild() called during build.` when combining overrides and async providers
- We need a pattern to flow HOT 3
- Add AsyncValue documentation HOT 2
- Add dependency injection doc HOT 2
- Add WidgetRef documentation HOT 2
- await ref.watch(streamProvider.future); resolves on the first yield HOT 3
- What is the recommended way of watching derived values of state exposed through methods ? There's no mention of this in docs HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from riverpod.