TextArea and TextInput can't be pre-populated with value

What package(s) are you using?

• carbon-components - 10.3.0
• carbon-components-react - 7.3.0

Detailed description

Since I’ve updated carbon-components to 10.3.0 and carbon-components-react to 7.3.0, both the TextInput and the TextArea components don’t initially pass value props down to the actual elements - which means the fields cannot be prepopulated.

This does not happen in previous versions - to see this yourself, use the CodeSandbox below and use 10.2.0/7.2.0. There, the fields are populated with whatever you pass as value to the Carbon component.

I can see the issue in the latest Chrome and Firefox.

Steps to reproduce the issue

See this reduced code snippet in CodeSandbox.

Notes

When looking at the tree using the React DevTools, you can see the Carbon components receive the value prop, but the <input>/<textarea> elements always get an empty string for their value.

[EAlexRojas]

Hi everybody, The PR https://github.com/carbon-design-system/carbon/pull/3015 did not fix the issue. It actually introduced a regression.

I created examples based in the code snipped in this issue, both use the same code but different versions of carbon-components / carbon-components-react:

• Working in version 10.2.0 / 7.2.0: https://codesandbox.io/s/carbon-components-react-730-textinputtextarea-value-ufci6
• Not working int version 10.3.1 / 7.3.1: https://codesandbox.io/s/carbon-components-react-730-textinputtextarea-value-z63zr

I think that the main issue is that the value prop is being ignored.

value prop is part of others (https://github.com/carbon-design-system/carbon/blob/master/packages/react/src/components/TextArea/TextArea.js#L51) but then, the value passed to the actual textarea is an internal state (initialized now with ‘defaultValue’) (https://github.com/carbon-design-system/carbon/blob/master/packages/react/src/components/TextArea/TextArea.js#L140)

Maybe, as in version 10.2.0 / 7.2.0, the value and defaultValue props should be just passed as is to the textarea (?) or at least initialize the internal state with the value from the value prop (?)

---

In any case, as you can see in the code snippets, there is a regression here. I hope this helps to find a solution.

@emyarod @asudoh

[emyarod]

defaultValue is already spread as a prop for the input field but it’s just not being taken as the initial state since the hooks refactor. given that we’ve been supporting defaultValue as a prop for multiple versions now, I’m going to leave the API unchanged and just pass defaultValue in as the initial value for the components