[PLAY-91] Add unique key prop to text input

[kyleschechter]

Screens

Breaking Changes

No. A unique key prop was added to the actual input element of the Text Input kit, clearing the error message that usually persists in the console when working with this kit in React.

Runway Ticket URL

https://nitro.powerhrg.com/runway/backlog_items/PLAY-91

How to test this

1. Navigate to http://localhost:3000/kits/text_input/react
2. Open console log
3. Check to make sure error is not there anymore

Checklist:

• LABELS Add a label: enhancement, bug, improvement, new kit, deprecated, or breaking. See Changelog & Labels for details.
• DEPLOY Please add the Milano label when you are ready for a review.
• SCREENSHOT Please add a screen shot or two.
• SPECS Please cover your changes with specs.
• READ DOCS Please make sure you have read and understand the Playbook Release Process

[thestephenmarshall]

After thinking about this more, if there is not a default then the key will always be the _className prop string which will not be unique.

[kyleschechter]

@thestephenmarshall Is there ever going to be a scenario where there isn't an 'id'? I just figured there would always be one. If not though, I can look into a function or something to generate unique id's.

[thestephenmarshall]

@kyleschechter of course there could be. Here you have an optional prop which means it can be undefined. And here you have no default value.