Component id requirements about patternfly-yew HOT 3 OPEN

Yup, I know that IDs are currently not very well supported. I saw that the PF React stuff random IDs if they are missing, which would also be my preference. Then combine them as you suggested.

We already have the uuid crate on board. And having a v4 UUID should be fine. This is actually being used in some places already.

I am not sure if we can get away with our own type, as the ID needs to be stable during re-renders. So I guess an Option<String> should work, combined with use_memo to generated derived strings. Which is actually available as use_prop_id already (name could be improved).

We could add another use_prop_id_suffixed (again, naming!) which accepts the ID from the properties as well as a static suffix which will be added.

from patternfly-yew.

Yeah, I did actually find this a couple days ago. Was wondering about the use_memo portion of it, the id shouldn't change right?

from patternfly-yew.

Right, the id shouldn't change. But if the Option is None, then one would need to create an alternative value (random) which should be memoized.

from patternfly-yew.