Eddy Wilson

It would be great if we could set in settings to only display instances of the current window or tab. Otherwise, it's difficult to know which is the instance of...

I'm not sure if that's easy to implement. As a workaround, maybe this works: ```javascript if (400 > data.lastX && !this.state.disableDragging) { this.setState({ ... disableDragging: true // disable here });...

👋 When a conditional rule is re-inserted, it shouldn't be removed or duplicated but it should be generated with a different classname. This also applies when they aren't re-inserted in...

@etc-tiago @kripod this proposal is a bit out of date 😅 Please check draft PR https://github.com/kripod/otion/pull/48 comments. It doesn't cause a breaking change with `css(...)` and it covers all cases...

No, the browser doesn't understand JSX, as explained in the blog posts, JSX needs to be transformed to function calls (`React.createElement` or `Didact.createElement`) by a transpiler (Babel or TS). If...

You can also pass a signal as prop rather than a value. It's similar how with `useState` you'd pass the value and setState function to a child component. The difference...

Hm, `useSignal` is kinda like `useState` and `useComputed` is more like `useMemo` where the deps are signals. I think maybe it'd make sense for `useComputed` to also accept a deps...

Signals use versioning internally, each update increases a version number, so the value isn't really used to know if a computed or effect should update. With that in mind, you...

Closing in favor of #265 After fixing a couple of issues I haven't considered, the performance isn't _that_ impressive anymore (at least to justify the +80 bytes) lol - PR...

As I understand by working with the internals the last weeks, `batch` doesn't batch updates but rather batches effects, it works sort of like this: ``` batch(() => { foo.value...