Added baselines.
This commit is contained in:
parent
1dca5620f5
commit
a1b90f0e32
8 changed files with 164 additions and 12 deletions
|
@ -1765,7 +1765,26 @@ declare module "typescript" {
|
||||||
classification: TokenClass;
|
classification: TokenClass;
|
||||||
}
|
}
|
||||||
interface Classifier {
|
interface Classifier {
|
||||||
getClassificationsForLine(text: string, lexState: EndOfLineState, syntacticClassifierAbsent?: boolean): ClassificationResult;
|
/**
|
||||||
|
* Gives lexical classifications of tokens on a line without any syntactic context.
|
||||||
|
* For instance, a token consisting of the text 'string' can be either an identifier
|
||||||
|
* named 'string' or the keyword 'string', however, because this classifier is not aware,
|
||||||
|
* it relies on certain heuristics to give acceptable results. For classifications where
|
||||||
|
* speed trumps accuracy, this function is preferable; however, for true accuracy, the
|
||||||
|
* syntactic classifier is ideal. In fact, in certain editing scenarios, combining the
|
||||||
|
* lexical, syntactic, and semantic classifiers may issue the best user experience.
|
||||||
|
*
|
||||||
|
* @param text The text of a line to classify.
|
||||||
|
* @param lexState The state of the lexical classifier at the end of the previous line.
|
||||||
|
* @param syntacticClassifierAbsent Whether the client is *not* using a syntactic classifier.
|
||||||
|
* If there is no syntactic classifier (syntacticClassifierAbsent=true),
|
||||||
|
* certain heuristics may be used in its place; however, if there is a
|
||||||
|
* syntactic classifier (syntacticClassifierAbsent=false), certain
|
||||||
|
* classifications which may be incorrectly categorized will be given
|
||||||
|
* back as Identifiers in order to allow the syntactic classifier to
|
||||||
|
* subsume the classification.
|
||||||
|
*/
|
||||||
|
getClassificationsForLine(text: string, lexState: EndOfLineState, syntacticClassifierAbsent: boolean): ClassificationResult;
|
||||||
}
|
}
|
||||||
/**
|
/**
|
||||||
* The document registry represents a store of SourceFile objects that can be shared between
|
* The document registry represents a store of SourceFile objects that can be shared between
|
||||||
|
|
|
@ -5603,8 +5603,27 @@ declare module "typescript" {
|
||||||
interface Classifier {
|
interface Classifier {
|
||||||
>Classifier : Classifier
|
>Classifier : Classifier
|
||||||
|
|
||||||
getClassificationsForLine(text: string, lexState: EndOfLineState, syntacticClassifierAbsent?: boolean): ClassificationResult;
|
/**
|
||||||
>getClassificationsForLine : (text: string, lexState: EndOfLineState, syntacticClassifierAbsent?: boolean) => ClassificationResult
|
* Gives lexical classifications of tokens on a line without any syntactic context.
|
||||||
|
* For instance, a token consisting of the text 'string' can be either an identifier
|
||||||
|
* named 'string' or the keyword 'string', however, because this classifier is not aware,
|
||||||
|
* it relies on certain heuristics to give acceptable results. For classifications where
|
||||||
|
* speed trumps accuracy, this function is preferable; however, for true accuracy, the
|
||||||
|
* syntactic classifier is ideal. In fact, in certain editing scenarios, combining the
|
||||||
|
* lexical, syntactic, and semantic classifiers may issue the best user experience.
|
||||||
|
*
|
||||||
|
* @param text The text of a line to classify.
|
||||||
|
* @param lexState The state of the lexical classifier at the end of the previous line.
|
||||||
|
* @param syntacticClassifierAbsent Whether the client is *not* using a syntactic classifier.
|
||||||
|
* If there is no syntactic classifier (syntacticClassifierAbsent=true),
|
||||||
|
* certain heuristics may be used in its place; however, if there is a
|
||||||
|
* syntactic classifier (syntacticClassifierAbsent=false), certain
|
||||||
|
* classifications which may be incorrectly categorized will be given
|
||||||
|
* back as Identifiers in order to allow the syntactic classifier to
|
||||||
|
* subsume the classification.
|
||||||
|
*/
|
||||||
|
getClassificationsForLine(text: string, lexState: EndOfLineState, syntacticClassifierAbsent: boolean): ClassificationResult;
|
||||||
|
>getClassificationsForLine : (text: string, lexState: EndOfLineState, syntacticClassifierAbsent: boolean) => ClassificationResult
|
||||||
>text : string
|
>text : string
|
||||||
>lexState : EndOfLineState
|
>lexState : EndOfLineState
|
||||||
>EndOfLineState : EndOfLineState
|
>EndOfLineState : EndOfLineState
|
||||||
|
|
|
@ -1796,7 +1796,26 @@ declare module "typescript" {
|
||||||
classification: TokenClass;
|
classification: TokenClass;
|
||||||
}
|
}
|
||||||
interface Classifier {
|
interface Classifier {
|
||||||
getClassificationsForLine(text: string, lexState: EndOfLineState, syntacticClassifierAbsent?: boolean): ClassificationResult;
|
/**
|
||||||
|
* Gives lexical classifications of tokens on a line without any syntactic context.
|
||||||
|
* For instance, a token consisting of the text 'string' can be either an identifier
|
||||||
|
* named 'string' or the keyword 'string', however, because this classifier is not aware,
|
||||||
|
* it relies on certain heuristics to give acceptable results. For classifications where
|
||||||
|
* speed trumps accuracy, this function is preferable; however, for true accuracy, the
|
||||||
|
* syntactic classifier is ideal. In fact, in certain editing scenarios, combining the
|
||||||
|
* lexical, syntactic, and semantic classifiers may issue the best user experience.
|
||||||
|
*
|
||||||
|
* @param text The text of a line to classify.
|
||||||
|
* @param lexState The state of the lexical classifier at the end of the previous line.
|
||||||
|
* @param syntacticClassifierAbsent Whether the client is *not* using a syntactic classifier.
|
||||||
|
* If there is no syntactic classifier (syntacticClassifierAbsent=true),
|
||||||
|
* certain heuristics may be used in its place; however, if there is a
|
||||||
|
* syntactic classifier (syntacticClassifierAbsent=false), certain
|
||||||
|
* classifications which may be incorrectly categorized will be given
|
||||||
|
* back as Identifiers in order to allow the syntactic classifier to
|
||||||
|
* subsume the classification.
|
||||||
|
*/
|
||||||
|
getClassificationsForLine(text: string, lexState: EndOfLineState, syntacticClassifierAbsent: boolean): ClassificationResult;
|
||||||
}
|
}
|
||||||
/**
|
/**
|
||||||
* The document registry represents a store of SourceFile objects that can be shared between
|
* The document registry represents a store of SourceFile objects that can be shared between
|
||||||
|
|
|
@ -5747,8 +5747,27 @@ declare module "typescript" {
|
||||||
interface Classifier {
|
interface Classifier {
|
||||||
>Classifier : Classifier
|
>Classifier : Classifier
|
||||||
|
|
||||||
getClassificationsForLine(text: string, lexState: EndOfLineState, syntacticClassifierAbsent?: boolean): ClassificationResult;
|
/**
|
||||||
>getClassificationsForLine : (text: string, lexState: EndOfLineState, syntacticClassifierAbsent?: boolean) => ClassificationResult
|
* Gives lexical classifications of tokens on a line without any syntactic context.
|
||||||
|
* For instance, a token consisting of the text 'string' can be either an identifier
|
||||||
|
* named 'string' or the keyword 'string', however, because this classifier is not aware,
|
||||||
|
* it relies on certain heuristics to give acceptable results. For classifications where
|
||||||
|
* speed trumps accuracy, this function is preferable; however, for true accuracy, the
|
||||||
|
* syntactic classifier is ideal. In fact, in certain editing scenarios, combining the
|
||||||
|
* lexical, syntactic, and semantic classifiers may issue the best user experience.
|
||||||
|
*
|
||||||
|
* @param text The text of a line to classify.
|
||||||
|
* @param lexState The state of the lexical classifier at the end of the previous line.
|
||||||
|
* @param syntacticClassifierAbsent Whether the client is *not* using a syntactic classifier.
|
||||||
|
* If there is no syntactic classifier (syntacticClassifierAbsent=true),
|
||||||
|
* certain heuristics may be used in its place; however, if there is a
|
||||||
|
* syntactic classifier (syntacticClassifierAbsent=false), certain
|
||||||
|
* classifications which may be incorrectly categorized will be given
|
||||||
|
* back as Identifiers in order to allow the syntactic classifier to
|
||||||
|
* subsume the classification.
|
||||||
|
*/
|
||||||
|
getClassificationsForLine(text: string, lexState: EndOfLineState, syntacticClassifierAbsent: boolean): ClassificationResult;
|
||||||
|
>getClassificationsForLine : (text: string, lexState: EndOfLineState, syntacticClassifierAbsent: boolean) => ClassificationResult
|
||||||
>text : string
|
>text : string
|
||||||
>lexState : EndOfLineState
|
>lexState : EndOfLineState
|
||||||
>EndOfLineState : EndOfLineState
|
>EndOfLineState : EndOfLineState
|
||||||
|
|
|
@ -1797,7 +1797,26 @@ declare module "typescript" {
|
||||||
classification: TokenClass;
|
classification: TokenClass;
|
||||||
}
|
}
|
||||||
interface Classifier {
|
interface Classifier {
|
||||||
getClassificationsForLine(text: string, lexState: EndOfLineState, syntacticClassifierAbsent?: boolean): ClassificationResult;
|
/**
|
||||||
|
* Gives lexical classifications of tokens on a line without any syntactic context.
|
||||||
|
* For instance, a token consisting of the text 'string' can be either an identifier
|
||||||
|
* named 'string' or the keyword 'string', however, because this classifier is not aware,
|
||||||
|
* it relies on certain heuristics to give acceptable results. For classifications where
|
||||||
|
* speed trumps accuracy, this function is preferable; however, for true accuracy, the
|
||||||
|
* syntactic classifier is ideal. In fact, in certain editing scenarios, combining the
|
||||||
|
* lexical, syntactic, and semantic classifiers may issue the best user experience.
|
||||||
|
*
|
||||||
|
* @param text The text of a line to classify.
|
||||||
|
* @param lexState The state of the lexical classifier at the end of the previous line.
|
||||||
|
* @param syntacticClassifierAbsent Whether the client is *not* using a syntactic classifier.
|
||||||
|
* If there is no syntactic classifier (syntacticClassifierAbsent=true),
|
||||||
|
* certain heuristics may be used in its place; however, if there is a
|
||||||
|
* syntactic classifier (syntacticClassifierAbsent=false), certain
|
||||||
|
* classifications which may be incorrectly categorized will be given
|
||||||
|
* back as Identifiers in order to allow the syntactic classifier to
|
||||||
|
* subsume the classification.
|
||||||
|
*/
|
||||||
|
getClassificationsForLine(text: string, lexState: EndOfLineState, syntacticClassifierAbsent: boolean): ClassificationResult;
|
||||||
}
|
}
|
||||||
/**
|
/**
|
||||||
* The document registry represents a store of SourceFile objects that can be shared between
|
* The document registry represents a store of SourceFile objects that can be shared between
|
||||||
|
|
|
@ -5699,8 +5699,27 @@ declare module "typescript" {
|
||||||
interface Classifier {
|
interface Classifier {
|
||||||
>Classifier : Classifier
|
>Classifier : Classifier
|
||||||
|
|
||||||
getClassificationsForLine(text: string, lexState: EndOfLineState, syntacticClassifierAbsent?: boolean): ClassificationResult;
|
/**
|
||||||
>getClassificationsForLine : (text: string, lexState: EndOfLineState, syntacticClassifierAbsent?: boolean) => ClassificationResult
|
* Gives lexical classifications of tokens on a line without any syntactic context.
|
||||||
|
* For instance, a token consisting of the text 'string' can be either an identifier
|
||||||
|
* named 'string' or the keyword 'string', however, because this classifier is not aware,
|
||||||
|
* it relies on certain heuristics to give acceptable results. For classifications where
|
||||||
|
* speed trumps accuracy, this function is preferable; however, for true accuracy, the
|
||||||
|
* syntactic classifier is ideal. In fact, in certain editing scenarios, combining the
|
||||||
|
* lexical, syntactic, and semantic classifiers may issue the best user experience.
|
||||||
|
*
|
||||||
|
* @param text The text of a line to classify.
|
||||||
|
* @param lexState The state of the lexical classifier at the end of the previous line.
|
||||||
|
* @param syntacticClassifierAbsent Whether the client is *not* using a syntactic classifier.
|
||||||
|
* If there is no syntactic classifier (syntacticClassifierAbsent=true),
|
||||||
|
* certain heuristics may be used in its place; however, if there is a
|
||||||
|
* syntactic classifier (syntacticClassifierAbsent=false), certain
|
||||||
|
* classifications which may be incorrectly categorized will be given
|
||||||
|
* back as Identifiers in order to allow the syntactic classifier to
|
||||||
|
* subsume the classification.
|
||||||
|
*/
|
||||||
|
getClassificationsForLine(text: string, lexState: EndOfLineState, syntacticClassifierAbsent: boolean): ClassificationResult;
|
||||||
|
>getClassificationsForLine : (text: string, lexState: EndOfLineState, syntacticClassifierAbsent: boolean) => ClassificationResult
|
||||||
>text : string
|
>text : string
|
||||||
>lexState : EndOfLineState
|
>lexState : EndOfLineState
|
||||||
>EndOfLineState : EndOfLineState
|
>EndOfLineState : EndOfLineState
|
||||||
|
|
|
@ -1834,7 +1834,26 @@ declare module "typescript" {
|
||||||
classification: TokenClass;
|
classification: TokenClass;
|
||||||
}
|
}
|
||||||
interface Classifier {
|
interface Classifier {
|
||||||
getClassificationsForLine(text: string, lexState: EndOfLineState, syntacticClassifierAbsent?: boolean): ClassificationResult;
|
/**
|
||||||
|
* Gives lexical classifications of tokens on a line without any syntactic context.
|
||||||
|
* For instance, a token consisting of the text 'string' can be either an identifier
|
||||||
|
* named 'string' or the keyword 'string', however, because this classifier is not aware,
|
||||||
|
* it relies on certain heuristics to give acceptable results. For classifications where
|
||||||
|
* speed trumps accuracy, this function is preferable; however, for true accuracy, the
|
||||||
|
* syntactic classifier is ideal. In fact, in certain editing scenarios, combining the
|
||||||
|
* lexical, syntactic, and semantic classifiers may issue the best user experience.
|
||||||
|
*
|
||||||
|
* @param text The text of a line to classify.
|
||||||
|
* @param lexState The state of the lexical classifier at the end of the previous line.
|
||||||
|
* @param syntacticClassifierAbsent Whether the client is *not* using a syntactic classifier.
|
||||||
|
* If there is no syntactic classifier (syntacticClassifierAbsent=true),
|
||||||
|
* certain heuristics may be used in its place; however, if there is a
|
||||||
|
* syntactic classifier (syntacticClassifierAbsent=false), certain
|
||||||
|
* classifications which may be incorrectly categorized will be given
|
||||||
|
* back as Identifiers in order to allow the syntactic classifier to
|
||||||
|
* subsume the classification.
|
||||||
|
*/
|
||||||
|
getClassificationsForLine(text: string, lexState: EndOfLineState, syntacticClassifierAbsent: boolean): ClassificationResult;
|
||||||
}
|
}
|
||||||
/**
|
/**
|
||||||
* The document registry represents a store of SourceFile objects that can be shared between
|
* The document registry represents a store of SourceFile objects that can be shared between
|
||||||
|
|
|
@ -5872,8 +5872,27 @@ declare module "typescript" {
|
||||||
interface Classifier {
|
interface Classifier {
|
||||||
>Classifier : Classifier
|
>Classifier : Classifier
|
||||||
|
|
||||||
getClassificationsForLine(text: string, lexState: EndOfLineState, syntacticClassifierAbsent?: boolean): ClassificationResult;
|
/**
|
||||||
>getClassificationsForLine : (text: string, lexState: EndOfLineState, syntacticClassifierAbsent?: boolean) => ClassificationResult
|
* Gives lexical classifications of tokens on a line without any syntactic context.
|
||||||
|
* For instance, a token consisting of the text 'string' can be either an identifier
|
||||||
|
* named 'string' or the keyword 'string', however, because this classifier is not aware,
|
||||||
|
* it relies on certain heuristics to give acceptable results. For classifications where
|
||||||
|
* speed trumps accuracy, this function is preferable; however, for true accuracy, the
|
||||||
|
* syntactic classifier is ideal. In fact, in certain editing scenarios, combining the
|
||||||
|
* lexical, syntactic, and semantic classifiers may issue the best user experience.
|
||||||
|
*
|
||||||
|
* @param text The text of a line to classify.
|
||||||
|
* @param lexState The state of the lexical classifier at the end of the previous line.
|
||||||
|
* @param syntacticClassifierAbsent Whether the client is *not* using a syntactic classifier.
|
||||||
|
* If there is no syntactic classifier (syntacticClassifierAbsent=true),
|
||||||
|
* certain heuristics may be used in its place; however, if there is a
|
||||||
|
* syntactic classifier (syntacticClassifierAbsent=false), certain
|
||||||
|
* classifications which may be incorrectly categorized will be given
|
||||||
|
* back as Identifiers in order to allow the syntactic classifier to
|
||||||
|
* subsume the classification.
|
||||||
|
*/
|
||||||
|
getClassificationsForLine(text: string, lexState: EndOfLineState, syntacticClassifierAbsent: boolean): ClassificationResult;
|
||||||
|
>getClassificationsForLine : (text: string, lexState: EndOfLineState, syntacticClassifierAbsent: boolean) => ClassificationResult
|
||||||
>text : string
|
>text : string
|
||||||
>lexState : EndOfLineState
|
>lexState : EndOfLineState
|
||||||
>EndOfLineState : EndOfLineState
|
>EndOfLineState : EndOfLineState
|
||||||
|
|
Loading…
Reference in a new issue