-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Add secrets handling in UI #1313
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
were we going to do something where you had to click on something in order to be able to edit the secret, so that people didn't accidentally do it? I think we talked about that originally but maybe that was replaced by your suggestion in slack here:
when we try to modify password field - do we expect input to be cleared on every focus + key press? Or some other behaviour
if so that's fine for now.
@jamakase can we merge this? |
@cgardens I was investigating a bit how to handle it from UX point of view in a more appropriate form. Need to have small fix and then we can merge. |
2b353aa
to
3bc142c
Compare
* #1313 source google ads: write less logs * #1313 source google ads: upd changelog * #1313 source google ads: fix expected records * #1313 source google ads: rm unused call to init * #1313 source google ads: fix expected records * #1313 source google ads - bump sieve outside the loop * auto-bump connector version Co-authored-by: Octavia Squidington III <[email protected]>
Closes #1055
What
adds
type=password
for secrets