Skip to content
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

Email Field Is Rendering As Password For Credential Of Type 'GoData' #1545

Closed
1 of 2 tasks
elias-ba opened this issue Dec 7, 2023 · 0 comments · Fixed by OpenFn/adaptors#450
Closed
1 of 2 tasks
Assignees
Labels
bug Newly identified bug unplanned Items included in a existing sprint that weren't part of the initial Sprint backlog

Comments

@elias-ba
Copy link
Contributor

elias-ba commented Dec 7, 2023

Describe the bug A clear and concise description of what the bug is.

When creating a credential of type 'GoData', we see that the email field (in the form) displays the text as if it was a password field.

Version number The version of Lightning you have seen the bug on.

v0.11.0

I have reproduced this locally on main:

  • Yes
  • No

To Reproduce Steps to reproduce the behavior:

  1. Open the credential creation modal
  2. Select the 'GoData' type of credential
  3. Click continue
  4. See the form with API URL, Email, and Password
  5. Fill the Email field and see the text being hidden

Expected behavior A clear and concise description of what you expected to
happen.

The Email text shouldn't be hidden

Screenshots If applicable, add screenshots to help explain your problem.

Screenshot from 2023-12-07 13-24-38

@elias-ba elias-ba added the bug Newly identified bug label Dec 7, 2023
@NickOpenFn NickOpenFn added the unplanned Items included in a existing sprint that weren't part of the initial Sprint backlog label Dec 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Newly identified bug unplanned Items included in a existing sprint that weren't part of the initial Sprint backlog
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants