**IMPORTANT!** Before picking this up for the sprint, arrange a task breakdown for this with @Sarai-WMDE, as the work here can be parallelized
**States**
List of the states that the component should display, mapping the specs:
[] Disabled
[] ReadOnly (prefilled)
[] Loading
[] Error
[] Warning
**Note:**
* The inline loader tokens are created according to the naming convention and used to style it (TBD by @Sarai-WMDE)
* All states should be displayed in Storybook on the "All" page.
* This is development happening in Wikit, not the Mismatch Finder anymore.
* Pulled originally from https://phabricator.wikimedia.org/T287568
* Loading state: The loading state of the component needs to be implemented in this first iteration due to product needs (displaying that the user input is being processed). 1) The assumption is that the `loading` state can be developed as a `prop` (like `error` or `disabled`). 2) The inline loading bar is a small, separate component (most likely a mixin): should we implement both elements (text area + inline loading bar) as part of the same task?