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

prompt user for new credential if connection failed with login failed error #993

Merged
merged 2 commits into from
Sep 21, 2017

Conversation

llali
Copy link
Member

@llali llali commented Sep 20, 2017

  • If connection failed and it's "login failed" error, prompt user to get new credential, try connection using the new credential

TODO: have to add tests

private promptForRetryConnectWithDifferentCredentials(): PromiseLike<boolean> {
// Ask if the user would like to fix the profile
return this._vscodeWrapper.showErrorMessage(LocalizedConstants.msgPromptRetryConnectionDifferentCredentials
, LocalizedConstants.retryLabel).then(result => {
Copy link
Contributor

@kevcunnane kevcunnane Sep 20, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Minor: I'd just put this on 1 line even if it's a bit long #WontFix

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the long is too long so I get formatting error if I don't put them in to lines


In reply to: 140110249 [](ancestors = 140110249)

let connectionWithoutCredentials = Object.assign({}, connection, { user: '', password: '', emptyPasswordInput: false });
ConnectionCredentials.ensureRequiredPropertiesSet(
connectionWithoutCredentials,
true,
Copy link
Contributor

@kevcunnane kevcunnane Sep 20, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Minor: can you add comments for what these values are? A bunch of true / false / true makes it hard to read. #Resolved

@coveralls
Copy link

Coverage Status

Coverage decreased (-0.4%) to 64.896% when pulling 6ed0339 on fix/storingInvalidPAssword into 4bd5ee0 on master.

@coveralls
Copy link

coveralls commented Sep 20, 2017

Coverage Status

Coverage increased (+0.7%) to 66.048% when pulling 9abef66 on fix/storingInvalidPAssword into 4bd5ee0 on master.

@llali llali merged commit 610dfa8 into master Sep 21, 2017
@abist abist deleted the fix/storingInvalidPAssword branch October 14, 2019 20:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants