tonic-input without id causes value to be lost about components HOT 5 CLOSED

This is by design, but I'm not sure the developer experience is correct. Basically, id says, this is a significant component that should retain its state across re-renders. But, it's not intuitive, perhaps we should have an attribute that indicates this? maybe persistent=true?

from components.

Hmm, emphemereal=true might be a good option.

I think not persisting the state can lead to bad UX.

Is there a use case for not setting id on tonic-input ?

Cleaning the end users text upon reRender is a bad experience.

from components.

My suggested solution would be to add a check for props.id in the render method of tonic-input and throw an exception if it’s missing

from components.

Some inputs are optional, their values don't need to be remembered, but that might be the unimportant case. So we are saying we should just remember a component's state by default. I think that's pretty reasonable actually.

from components.

This is not possible to implement.

We can either :

• do the current behavior of only persisting state for Tonic components that have an id field
• Or add a new gaurd in the render() method of some components like tonic-input that make the id field mandatory and force developers to set it.

from components.