André Staltz

Hi @ntilwalli > I understand that currently the only way to remove an unused child component's property from the onion state is to have the parent set it's state value...

Okay I understand the use case now. I'm afraid doing what you asked is not possible, or at least would break other use cases. I can explain how. First note...

> André suggested, that memoization could help here, and it definitely will, but it doesn't look possible without introducing ids That's ok. IDs can be used as a way to...

I have some ideas for this, including one that would use diff and patch in order to know when to create a child component. I've done some experiments, but not...

@kylecordes check issue #28

Oh yeah, seems like the typings files for rx and most are very outdated. That was a mistake

> If I wrap them the other way, onion state is available inside the component instantiated by modalify - but modalify fails to work, for reasons I did not debug....

I think this is a bug which shouldn't happen with xstream (because it does sync start and async stop) but might happen with RxJS.

I wonder if this resetting happens because of the initial reducer being ```typescript const initReducer$ = xs.of(() => ({ active: false })); ``` Try using a default reducer instead. Which...

Hi! Do you have an account on DO? Note, however, that this repo is deprecated in favor of https://github.com/ssb-ngi-pointer/go-ssb-room/ which is better in all regards. I should update the README...