Ítalo Andrade comments

Results 34 comments of


                                            Ítalo Andrade

Customize what is going to be copied / Copy everything together

Hi @RodrigoHamuy, I'm not using `leva` at the moment. You can continue with this PR if you want. Let me know if you need any help.

Customize what is going to be copied / Copy everything together

I already started a POC with both implementations. You can check it on my fork: https://github.com/italodeandra/leva/commit/4a4c23eeb3af90685813477317601e6ed75c4d57

Customize what is going to be copied / Copy everything together

Hey @dbismut, Just did, you can check it here #193. I hope I didn't break anything, but let me know what needs to be changed.

MultiSelect with `searchable` and `creatable` hides caret when empty and hides new query when the query already exists

The first issue is when I'm focused on the MultiSelect with an item already added, my caret is hidden. It should be still visible the same way it is when...

MultiSelect with `searchable` and `creatable` hides caret when empty and hides new query when the query already exists

> You can configure this behavior with `filter` and `shouldCreate` props Sorry, I didn't get how these props can fix the issue. Can you elaborate, please?

MultiSelect with `searchable` and `creatable` hides caret when empty and hides new query when the query already exists

But the issue I mentioned happens on the search field (the query text), not in the options. You can check the video again to see better what I mean.

MultiSelect with `searchable` and `creatable` hides caret when empty and hides new query when the query already exists

Yes. It was fixed. Thanks!

Textarea with autosize shows scrollbar when the text still fit the `maxRow`

I've used the same package on previous personal UI libraries, and MUI also uses it and I've never seen this issue. Can you reopen the issue? I'll work on it...

Textarea with autosize shows scrollbar when the text still fit the `maxRow`

Hey Vitaly, I moved out of Mantine for personal reasons, so I won't be working on this issue anymore. I'm sorry man.

`useDeepCompareEffect` should not show the warning when the values are not primitive but `null`/`undefined` at the moment

Hey @HummingBird24. Thank you for the reply but in my opinion these are separate cases. I agree that changing something from `object` to `boolean` can cause problems. But changing something...