In the vets-website, there are several components, deprecating and new, that we have to account for when migrating the components to the Identity SDK Library.
However, one component in particular VaModal does not work in certain areas of the VA websites, which caused the issue of migrating from the deprecated component to the new web component from USWDS v3 not to work.
This ticket here is to track the progress of creating a custom component to be used within the Identity SDK Library first or attempt to use the one from the component-library instead, whichever comes first.
Move to backlog, will cover this in the near future if it is still necessary to create a web component alternative then what the VA component library has
Description
In the
vets-website
, there are several components, deprecating and new, that we have to account for when migrating the components to the Identity SDK Library.However, one component in particular
VaModal
does not work in certain areas of the VA websites, which caused the issue of migrating from the deprecated component to the new web component from USWDS v3 not to work.This ticket here is to track the progress of creating a custom component to be used within the Identity SDK Library first or attempt to use the one from the component-library instead, whichever comes first.