You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
// This flag will be set to true when the parse encounter dynamic import so that post-parsing process of module resolution
428
-
// will not walk the tree if the flag is not set. However, this flag is just a approximation because once it is set, the flag never get reset.
429
-
// (hence it is named "possiblyContainDynamicImport").
430
-
// During editing, if dynamic import is remove, incremental parsing will *NOT* update this flag. This will then causes walking of the tree during module resolution.
431
-
// However, the removal operation should not occur often and in the case of the removal, it is likely that users will add back the import anyway.
432
-
// The advantage of this approach is its simplicity. For the case of batch compilation, we garuntee that users won't have to pay the price of walking the tree if dynamic import isn't used.
var newSourceFile = IncrementalParser.updateSourceFile(sourceFile, newText, textChangeRange, aggressiveChecks);
16305
16308
// Because new source file node is created, it may not have the flag PossiblyContainDynamicImport. This is the case if there is no new edit to add dynamic import.
16306
16309
// We will manually port the flag to the new source file.
// This flag will be set to true when the parse encounter dynamic import so that post-parsing process of module resolution
428
-
// will not walk the tree if the flag is not set. However, this flag is just a approximation because once it is set, the flag never get reset.
429
-
// (hence it is named "possiblyContainDynamicImport").
430
-
// During editing, if dynamic import is remove, incremental parsing will *NOT* update this flag. This will then causes walking of the tree during module resolution.
431
-
// However, the removal operation should not occur often and in the case of the removal, it is likely that users will add back the import anyway.
432
-
// The advantage of this approach is its simplicity. For the case of batch compilation, we garuntee that users won't have to pay the price of walking the tree if dynamic import isn't used.
var newSourceFile = IncrementalParser.updateSourceFile(sourceFile, newText, textChangeRange, aggressiveChecks);
16305
16308
// Because new source file node is created, it may not have the flag PossiblyContainDynamicImport. This is the case if there is no new edit to add dynamic import.
16306
16309
// We will manually port the flag to the new source file.
0 commit comments