-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Post-merge review of #3356 #3379
Comments
I'm taking "auth". I pick anything but "session", because there is a layer of "[actOn]Session" methods that call to "[actOn]Secret" methods (that are kind of a lower level), that's why I took a different word for that. |
Do you mean adding a check on its value at runtime? |
More to just create a restricted type, e.g. export type SecretKeys =
| `gitlens.${AIProviders}.key`
| `gitlens.plus.auth:${Environment}`
| IntegrationAuthenticationKeys;
export type IntegrationAuthenticationKeys =
| `gitlens.integration.auth:${IntegrationId}|${string}`
| `gitlens.integration.auth.cloud:${IntegrationId}|${string}`; And then use that new type |
ok. that's clear |
(to "write/read/delete StoredSession") GLVSC-591 #3379
(to "write/read/delete StoredSession") GLVSC-591 #3379
(to "write/read/delete StoredSession") GLVSC-591 #3379
(to "write/read/delete StoredSession") GLVSC-591 #3379
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Review of #3356
Can we consolidate the following to hide that complexity inside the
integration.connect()
call?vscode-gitlens/src/commands/remoteProviders.ts
Lines 99 to 115 in 2f9750e
vscode-gitlens/src/plus/focus/focus.ts
Lines 162 to 177 in 2f9750e
Suggest changing the notion of "secret" to "session"/"stored session"/"auth":
vscode-gitlens/src/plus/integrations/authentication/integrationAuthentication.ts
Lines 71 to 96 in 305d406
Restrict the
key
params to be a subset ofSecretKeys
to avoid something else getting in therevscode-gitlens/src/plus/integrations/authentication/integrationAuthentication.ts
Lines 71 to 96 in 305d406
Generally avoid
Promise.all
and usePromose.allSettled
when we want to wait for everything -- asPromise.all
will throw on the first rejected promisehttps://gitkraken.atlassian.net/browse/GLVSC-591
The text was updated successfully, but these errors were encountered: