Sasha Khamkov

I actually think the bug is on the other block. And the bug is the way props being set - e.g. not in as the callback of setState.

@RookY2K I looked at it a bit from the internal state perspective. I think it is not able to update because react is guarding itself from doing update while other...

Bug on RDS or not, I never said it was an issue on react, I think it is prevention of loop. I might be wrong. But updating state and triggering...

> Functional component rewrite indeed will be a huge change. But this is something that will need to happened. Eventually they will stop supporting lifecycles I guess.

> I just wanted to make sure that the bug was brought to your attention And I appreciate it.

All is good 😊

Can you suggest a PR that is working on your scenario? I think the behavior you describing is correct. On Fri, Jul 7, 2023, 4:17 PM NishilSB ***@***.***> wrote: >...

Hey, try to add name property to the select. It should be playing better with forms. [Example](https://react-dropdown-select.netlify.app/examples#Form-with-validation-(using-react-live)) and source: https://github.com/sanusart/react-dropdown-select/blob/master/docs/src/examples/Form.js#L14

Ah. I think I misunderstood the initial post. Select component is controlled, meaning the consumer is in charge to implement its own onChange tactics. I think best bet is using...

It does not make sense from hi perspective to have two searches. More like here https://sanusart.github.io/react-dropdown-select/examples#Custom-Content-And-Dropdown-renderers The demo on home page just enables most of the features