-
Notifications
You must be signed in to change notification settings - Fork 29.7k
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
Make ExtensionTipsService multi-root aware #32106
Make ExtensionTipsService multi-root aware #32106
Conversation
return []; | ||
}).then<string[]>(null, err => []) | ||
) | ||
).then(flatten); |
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.
Also needed to de dup
}, err => []); | ||
return TPromise.join( | ||
this.contextService.getWorkspace().roots.map(root => | ||
this.fileService.resolveContent(root.with({ path: root.path + '/.vscode/extensions.json' })).then(content => { |
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.
I would use the old way paths
to construct the path. This will make construct the path as per the platform
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.
That would use backslashes on Windows, which is not valid in a URI
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.
That would use backslashes on Windows
True, but it is a valid file path. Creating an URI using URI.file
takes care of it
Good thing is it will hide the knowledge of path separators.
Resolved the conflicts and pushed |
As described in #29242
Collects extension recommendations from all roots instead of only for the first root.