[shravani-0811]

Description

Added Files for showing and hiding password as a toggle button

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• I have signed the Adobe Open Source CLA.
• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.

[rismehta]

check comments

[sakshi-arora1]

The commit is confusing. As we are touching all the areas.

1. Create a new commit to make variables, if you want to make it more variable driven. But you need to make sure the values remain same, as any change can actually break production forms.
2. Create a separate commit for password

[iamsudhanshu]

The commit is confusing. As we are touching all the areas.

1. Create a new commit to make variables, if you want to make it more variable driven. But you need to make sure the values remain same, as any change can actually break production forms.
2. Create a separate commit for password

Checked the PR has 2 commits - with migration to variable in a separate commit - so we should be good. Also validated the variable replacement with copilot:

so if we do not squash and merge - we should be good, and we can share the specific commit with customers to integrate the password changes in their repos. @sakshi-arora1 could you confirm if we are good to merge in that case.

cc: @shravani-0811