Yoav Kadosh

Hi, it looks like you are having issues with filecons, but I can’t read Chinese (and google translate does not do a very good job) > On Aug 7, 2015,...

Thank you for replying @loganfsmyth, I have updated my report with additional information, hope that clears things up

@hampustagerud this doesn't work when the subpackages have their own alias configuration using `module-resolver`. Does your monorepo have such configuration?

@hampustagerud That's exactly why it is working for you I guess. I have subpackages with the same alias pointing to **a different folder** (see my example - they all have...

This warning is indeed confusing. My guess is that snapshots can be arbitrarily removed from memory unless we call `retain()` on them. With that in mind, we can modify their...

Having a component that is both controlled and uncontrolled can lead to many issues, and can become a maintenance nightmare. This is discouraged in the official [React docs](https://reactjs.org/blog/2018/06/07/you-probably-dont-need-derived-state.html#common-bugs-when-using-derived-state) (they refer...

I see, how about creating a small component for that? Something like: ```jsx const Details = ({children, title}) => { const {visible, toggle} = useVisibilityState(); return ( {title} {children} );...

Hi @DieTapete There are a few issues with your example: 1. You're not passing a `reference` to ``, which is why you're modal is hidden. You should pass it like...

I see now that you wanted it to appear at `[0,0]`, and indeed it considers it to be `hidden` in that case. @yairEO we use `[0,0]` as a `hidden` placement...

@yairEO I don't recall all the original reasoning, but the `HIDDEN_PLACEMENT` is used both for hiding the `` (initially or when the target is missing), and as a communication device...