Reintroduce password type to auth inputs #1039
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Reintroduces password type to API key/token input fields. Although credentials will still be plain text in code snippets, we could at least mask them in the form input.
Motivation and Context
Could be helpful to mask API key/token or passwords when performing a live demo or screen recording. Next step is to find a viable approach to mask or obfuscate them in code snippets without breaking the underlying request.
How Has This Been Tested?
Tested locally in dev. See deploy preview for production test.
Screenshots (if appropriate)
See deploy preview
Types of changes