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
I was trying to use a different icon library by changing the vuestic configuration as in the documentation, I disabled the material design icons because I don't want to use them in my project and wanted to work with phosphor icons instead. I did changed my config as follows:
But then, when I was working with the VaInput component I found something odd: the form input was showing a red text on error instead of an icon from the phosphor library that I have setup previously.
I tried searching for props in the input component but I was a bit disappointed to find that there was no error or warning icon name options.
Upon inspecting the code I found the culprit here:
m0ksem
changed the title
VaInputWrapper Icons are hard coded, can't switch from materialdesign icons
docs: add notice that user needs to update aliases when adding new font
Jun 30, 2024
Overview of the problem
I was trying to use a different icon library by changing the vuestic configuration as in the documentation, I disabled the material design icons because I don't want to use them in my project and wanted to work with phosphor icons instead. I did changed my config as follows:
But then, when I was working with the VaInput component I found something odd: the form input was showing a red text on error instead of an icon from the phosphor library that I have setup previously.
I tried searching for props in the input component but I was a bit disappointed to find that there was no error or warning icon name options.
Upon inspecting the code I found the culprit here:
vuestic-ui/packages/ui/src/components/va-input-wrapper/VaInputWrapper.vue
Lines 69 to 87 in eef4a96
Possible Solutions
It's easy to solve:
Add warningIconName, successIconName, loadingIconName as a prop on VaInput and pass it down to the VaInputWrapper.
The text was updated successfully, but these errors were encountered: