-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reusable UI Components ( buttons, search inputs, input fields - with password toggling icons, and text areas ) . #87
Comments
can this issue be assigned to me @Vin-Jex |
Which issue do you want to be assigned to? |
@Vin-Jex Hey, I agree with the reusable components methodology and I'd like to create the components (any or all) as per the web-app design. Please assign it to me. |
Of course, I will assign it to you. |
@parth10-1 I will open this issue if you fail to create a PR on this soon. Thank you! |
Sure, of course. |
I haven't been able to make time for this and am a bit busy henceforth. I have unassigned myself. Cheers. |
@Vin-Jex I'd like to be assigned to this issue of creating reusable components. Please assign it to me. |
Is your feature request related to a problem? Please describe.
Currently, we lack consistent and reusable UI components for buttons, input fields, and text areas throughout the application. This leads to inconsistent styles and behavior, which can be frustrating when trying to maintain a uniform user experience.
Describe the solution you'd like
I propose creating a set of reusable components that include:
These components should be designed to ensure a cohesive look and feel while improving maintainability.
Describe alternatives you've considered
An alternative would be to continue using ad-hoc components across the application, but this approach risks further inconsistencies and makes future updates more challenging.
The text was updated successfully, but these errors were encountered: