You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I was first creating the ui-flags component (the component which renders fields within a particular CLI schematic), Angular material did not yet have its "outline" style form fields (see https://stackblitz.com/edit/angular-uhbbyu?file=app/form-field-label-example.html for an example). Now that it does, we should use it instead of the custom rounded form fields that I hacked together initially. The benefits are not having brittle CSS that can break with angular material releases, using the built-in mat-hint component rather than absolutely positioning our hints per flag type and overall a better UI experience.
This will be an easy change for autocomplete-able, text-based and select flag types. A bit of custom work will need to be done for boolean types (maybe we should just represent these as dropdowns with two items or maybe we do something custom so they remain clickable toggles).
In addition to using outline based form fields the UI forms could use some general UI touchups. Adding more whitespace to increase readability and potentially adding another column to the form for screens which are particularly wide. These and other tweaks can be left to whoever takes on this issue.
The text was updated successfully, but these errors were encountered:
When I was first creating the ui-flags component (the component which renders fields within a particular CLI schematic), Angular material did not yet have its "outline" style form fields (see https://stackblitz.com/edit/angular-uhbbyu?file=app/form-field-label-example.html for an example). Now that it does, we should use it instead of the custom rounded form fields that I hacked together initially. The benefits are not having brittle CSS that can break with angular material releases, using the built-in mat-hint component rather than absolutely positioning our hints per flag type and overall a better UI experience.
This will be an easy change for autocomplete-able, text-based and select flag types. A bit of custom work will need to be done for boolean types (maybe we should just represent these as dropdowns with two items or maybe we do something custom so they remain clickable toggles).
In addition to using outline based form fields the UI forms could use some general UI touchups. Adding more whitespace to increase readability and potentially adding another column to the form for screens which are particularly wide. These and other tweaks can be left to whoever takes on this issue.
The text was updated successfully, but these errors were encountered: