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
The va-number-input component has incrementally expanded in function to the point where there is little difference between the purpose it serves and that which our va-text-input fills. Even now, issues exist for requests to broadened the abilities va-number-input offers. With this, the va-number-input will be deprecated, and it's existing functionality will be subsumed by the va-text-input.
This is a multi-step process that will involve:
Updating the va-text-input component with any va-number-input functionality it doesn't already cover
Updating the storybook guidance for va-text-input
Providing teams with a timeline and migration plan for when va-number-input will be replaced in vets-website
Releasing the update to vets-website.
Considerations:
There are currently 28 combined instances of va-number-input and VaNumberInput being used in vets-website
The text was updated successfully, but these errors were encountered:
Description
The
va-number-input
component has incrementally expanded in function to the point where there is little difference between the purpose it serves and that which ourva-text-input
fills. Even now, issues exist for requests to broadened the abilitiesva-number-input
offers. With this, theva-number-input
will be deprecated, and it's existing functionality will be subsumed by theva-text-input
.This is a multi-step process that will involve:
va-text-input
component with anyva-number-input
functionality it doesn't already coverva-text-input
va-number-input
will be replaced in vets-websiteConsiderations:
va-number-input
andVaNumberInput
being used in vets-websiteThe text was updated successfully, but these errors were encountered: