@cycle/proxy idea for circular dependecy
See original GitHub issueAfter discussion with @TylorS what about such api for proxying curcular deps?
import proxy from '@cycle/proxy'
//...
function MyComponent () {
const {imitate, stream} = proxy()
const componentFoo = ComponentFoo({stream, DOM})
const componentBar = ComponentBar({HTTP, componentFoo.props$})
imitate(componentBar.value$)
as alternative to https://github.com/cyclejs/core/issues/170
Issue Analytics
- State:
- Created 7 years ago
- Comments:24 (18 by maintainers)
Top Results From Across the Web
Circular Dependencies in Dependency Injection - Medium
A description of how we solved a circular dependency in our dependency injection, and some of the software principles involved.
Read more >Circular Dependencies in Spring - Baeldung
A quick writeup on dealing with circular dependencies in Spring: how they occur and several ways to work around them.
Read more >How to solve cyclic dependency between different modules in ...
Go to project-> java compiler-> building -> Enable project specific settings. Select build path problems and give warning as option for circular ......
Read more >Circular Dependencies in C++ - pvigier's blog
Its goal is to draw the “include” dependencies between classes in a C++ project. In particular, it allows to detect circular dependencies ......
Read more >How to solve circular dependency?
There may be more variants to approach your problem, but I hope you get the general idea: your core problem are classes with...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Honestly, I’m not a fan of the idea because it’s turning Babel into a DSL generator rather than a tool for getting early access to general language features. By using a plugin, you make Babel into a hard dependency for a Cycle app.
Of course, and people can do what they like with their own apps, but my point is with respect to core functionality being only available via a Babel plugin. People may want to solve the problem without being cornered into the land of Babel plugins. If there’s a generic, non-plugin solution though, then there’s no issue.
Here’s an (as-yet-untested) implementation of the hypothetical helper in my example above. Note that
makeStreamProxy
would need an RxJS implementation. Mine is based on the Most.js version by @TylorS.