-
-
Notifications
You must be signed in to change notification settings - Fork 52
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
Clean up and document createLanguageServicePlugin
and createAsyncLanguageServicePlugin
#261
base: master
Are you sure you want to change the base?
Conversation
.map(plugin => plugin.typescript?.extraFileExtensions.map(ext => '.' + ext.extension) ?? []) | ||
.flat(); | ||
|
||
// TODO: this logic does not seem to appear in the async variant | ||
// (createAsyncLanguageServicePlugin)... bug? |
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.
OPEN QUESTION: is it a bug that the async variant (createAsyncLanguageServicePlugin
) does not add the extensions passed in to projectExternalFileExtensions
? (This is also how it was prior to this PR).
if (updateLevel >= (1 satisfies ts.ProgramUpdateLevel.RootNamesAndUpdate) | ||
|| !externalFiles.has(project)) { | ||
const oldFiles = externalFiles.get(project); | ||
const extensions = projectExternalFileExtensions.get(project); |
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.
This is where we check projectExternalFileExtensions
(see other comment)
No description provided.