Incremented `id` doesn't play nicely w/ SSR

[templarian]

Incremented `id` doesn't play nicely w/ SSR

[Templarian]

This was published @mAAdhaTTah @shabith! I really need to setup something that reminds me of this stuff. An AI to better manage my open source stuff. Like "That one repo that you never check has stuff."

Sorry about that!

[Templarian]

@mAAdhaTTah Is there a convention for this prop name possibly you've seen elsewhere. Definitely would take a PR for this.

I'm assuming a lot of components run into this if you can find an example somewhere else that will make me feel better about the change.

[mAAdhaTTah]

@Templarian Personally, I think id would be fine, since that's the underlying attribute. For other examples, we ran into a similar issues with Downshift, which uses id and will generate a default value if one isn't provided.

[Templarian]

@mAAdhaTTah It looks like they try to solve this issue with useOpaqueIdentifier. I'm fine merging a PR that takes in an id.

[Templarian]

Going to re-open this until I have it published to NPM.

@mAAdhaTTah Annoy me if this is not published by Saturday afternoon please.

[mAAdhaTTah]

@Templarian Will do, thank you!

[mAAdhaTTah]

@Templarian Hope you're having a great weekend! Obvs I didn't tag you on this last weekend but maybe you have some time this one?

[shabith]

Hi @Templarian any update on this? seems like it is not published to NPM yet.

Thanks @mAAdhaTTah for your PR on this.

[bdemirel]

I was facing the same problem and took me some time to find this issue/PR. Thanks for the fix, but it may be useful to add a note about this on the website!