Using the same principle of https://github.com/olmps/memo/issues/224, recently designed TextFields aren't following Material guidelines, which mean that we must implement a custom Widget to achieve such visual style.
This component could be a wrapper in the native TextField, while adding the visual style on top of it. Doing like so lets us benefit from the native TextField implementation features.
Business Rules
It must respect the visual behavior specified in the Figma project, which are visually explained in the state screenshots below
Screenhots
TextField states
![CleanShot 2021-10-29 at 09 27 25](https://user-images.githubusercontent.com/11745745/139434343-652fc051-f0cd-4134-9ba6-928bd5dc765f.png)
Summary
Using the same principle of https://github.com/olmps/memo/issues/224, recently designed
TextField
s aren't followingMaterial
guidelines, which mean that we must implement a custom Widget to achieve such visual style.This component could be a wrapper in the native
TextField
, while adding the visual style on top of it. Doing like so lets us benefit from the native TextField implementation features.Business Rules
It must respect the visual behavior specified in the Figma project, which are visually explained in the state screenshots below
Screenhots
TextField states
![CleanShot 2021-10-29 at 09 27 25](https://user-images.githubusercontent.com/11745745/139434343-652fc051-f0cd-4134-9ba6-928bd5dc765f.png)