Skip to content

Commit a1b90f0

Browse files
DanielRosenwasserDanielRosenwasser
committed
Added baselines.
1 parent 1dca562 commit a1b90f0

8 files changed

+164
-12
lines changed

Diff for: ‎tests/baselines/reference/APISample_compile.js

+20-1
Original file line numberDiff line numberDiff line change
@@ -1765,7 +1765,26 @@ declare module "typescript" {
17651765
classification: TokenClass;
17661766
}
17671767
interface Classifier {
1768-
getClassificationsForLine(text: string, lexState: EndOfLineState, syntacticClassifierAbsent?: boolean): ClassificationResult;
1768+
/**
1769+
* Gives lexical classifications of tokens on a line without any syntactic context.
1770+
* For instance, a token consisting of the text 'string' can be either an identifier
1771+
* named 'string' or the keyword 'string', however, because this classifier is not aware,
1772+
* it relies on certain heuristics to give acceptable results. For classifications where
1773+
* speed trumps accuracy, this function is preferable; however, for true accuracy, the
1774+
* syntactic classifier is ideal. In fact, in certain editing scenarios, combining the
1775+
* lexical, syntactic, and semantic classifiers may issue the best user experience.
1776+
*
1777+
* @param text The text of a line to classify.
1778+
* @param lexState The state of the lexical classifier at the end of the previous line.
1779+
* @param syntacticClassifierAbsent Whether the client is *not* using a syntactic classifier.
1780+
* If there is no syntactic classifier (syntacticClassifierAbsent=true),
1781+
* certain heuristics may be used in its place; however, if there is a
1782+
* syntactic classifier (syntacticClassifierAbsent=false), certain
1783+
* classifications which may be incorrectly categorized will be given
1784+
* back as Identifiers in order to allow the syntactic classifier to
1785+
* subsume the classification.
1786+
*/
1787+
getClassificationsForLine(text: string, lexState: EndOfLineState, syntacticClassifierAbsent: boolean): ClassificationResult;
17691788
}
17701789
/**
17711790
* The document registry represents a store of SourceFile objects that can be shared between

Diff for: ‎tests/baselines/reference/APISample_compile.types

+21-2
Original file line numberDiff line numberDiff line change
@@ -5603,8 +5603,27 @@ declare module "typescript" {
56035603
interface Classifier {
56045604
>Classifier : Classifier
56055605

5606-
getClassificationsForLine(text: string, lexState: EndOfLineState, syntacticClassifierAbsent?: boolean): ClassificationResult;
5607-
>getClassificationsForLine : (text: string, lexState: EndOfLineState, syntacticClassifierAbsent?: boolean) => ClassificationResult
5606+
/**
5607+
* Gives lexical classifications of tokens on a line without any syntactic context.
5608+
* For instance, a token consisting of the text 'string' can be either an identifier
5609+
* named 'string' or the keyword 'string', however, because this classifier is not aware,
5610+
* it relies on certain heuristics to give acceptable results. For classifications where
5611+
* speed trumps accuracy, this function is preferable; however, for true accuracy, the
5612+
* syntactic classifier is ideal. In fact, in certain editing scenarios, combining the
5613+
* lexical, syntactic, and semantic classifiers may issue the best user experience.
5614+
*
5615+
* @param text The text of a line to classify.
5616+
* @param lexState The state of the lexical classifier at the end of the previous line.
5617+
* @param syntacticClassifierAbsent Whether the client is *not* using a syntactic classifier.
5618+
* If there is no syntactic classifier (syntacticClassifierAbsent=true),
5619+
* certain heuristics may be used in its place; however, if there is a
5620+
* syntactic classifier (syntacticClassifierAbsent=false), certain
5621+
* classifications which may be incorrectly categorized will be given
5622+
* back as Identifiers in order to allow the syntactic classifier to
5623+
* subsume the classification.
5624+
*/
5625+
getClassificationsForLine(text: string, lexState: EndOfLineState, syntacticClassifierAbsent: boolean): ClassificationResult;
5626+
>getClassificationsForLine : (text: string, lexState: EndOfLineState, syntacticClassifierAbsent: boolean) => ClassificationResult
56085627
>text : string
56095628
>lexState : EndOfLineState
56105629
>EndOfLineState : EndOfLineState

Diff for: ‎tests/baselines/reference/APISample_linter.js

+20-1
Original file line numberDiff line numberDiff line change
@@ -1796,7 +1796,26 @@ declare module "typescript" {
17961796
classification: TokenClass;
17971797
}
17981798
interface Classifier {
1799-
getClassificationsForLine(text: string, lexState: EndOfLineState, syntacticClassifierAbsent?: boolean): ClassificationResult;
1799+
/**
1800+
* Gives lexical classifications of tokens on a line without any syntactic context.
1801+
* For instance, a token consisting of the text 'string' can be either an identifier
1802+
* named 'string' or the keyword 'string', however, because this classifier is not aware,
1803+
* it relies on certain heuristics to give acceptable results. For classifications where
1804+
* speed trumps accuracy, this function is preferable; however, for true accuracy, the
1805+
* syntactic classifier is ideal. In fact, in certain editing scenarios, combining the
1806+
* lexical, syntactic, and semantic classifiers may issue the best user experience.
1807+
*
1808+
* @param text The text of a line to classify.
1809+
* @param lexState The state of the lexical classifier at the end of the previous line.
1810+
* @param syntacticClassifierAbsent Whether the client is *not* using a syntactic classifier.
1811+
* If there is no syntactic classifier (syntacticClassifierAbsent=true),
1812+
* certain heuristics may be used in its place; however, if there is a
1813+
* syntactic classifier (syntacticClassifierAbsent=false), certain
1814+
* classifications which may be incorrectly categorized will be given
1815+
* back as Identifiers in order to allow the syntactic classifier to
1816+
* subsume the classification.
1817+
*/
1818+
getClassificationsForLine(text: string, lexState: EndOfLineState, syntacticClassifierAbsent: boolean): ClassificationResult;
18001819
}
18011820
/**
18021821
* The document registry represents a store of SourceFile objects that can be shared between

Diff for: ‎tests/baselines/reference/APISample_linter.types

+21-2
Original file line numberDiff line numberDiff line change
@@ -5747,8 +5747,27 @@ declare module "typescript" {
57475747
interface Classifier {
57485748
>Classifier : Classifier
57495749

5750-
getClassificationsForLine(text: string, lexState: EndOfLineState, syntacticClassifierAbsent?: boolean): ClassificationResult;
5751-
>getClassificationsForLine : (text: string, lexState: EndOfLineState, syntacticClassifierAbsent?: boolean) => ClassificationResult
5750+
/**
5751+
* Gives lexical classifications of tokens on a line without any syntactic context.
5752+
* For instance, a token consisting of the text 'string' can be either an identifier
5753+
* named 'string' or the keyword 'string', however, because this classifier is not aware,
5754+
* it relies on certain heuristics to give acceptable results. For classifications where
5755+
* speed trumps accuracy, this function is preferable; however, for true accuracy, the
5756+
* syntactic classifier is ideal. In fact, in certain editing scenarios, combining the
5757+
* lexical, syntactic, and semantic classifiers may issue the best user experience.
5758+
*
5759+
* @param text The text of a line to classify.
5760+
* @param lexState The state of the lexical classifier at the end of the previous line.
5761+
* @param syntacticClassifierAbsent Whether the client is *not* using a syntactic classifier.
5762+
* If there is no syntactic classifier (syntacticClassifierAbsent=true),
5763+
* certain heuristics may be used in its place; however, if there is a
5764+
* syntactic classifier (syntacticClassifierAbsent=false), certain
5765+
* classifications which may be incorrectly categorized will be given
5766+
* back as Identifiers in order to allow the syntactic classifier to
5767+
* subsume the classification.
5768+
*/
5769+
getClassificationsForLine(text: string, lexState: EndOfLineState, syntacticClassifierAbsent: boolean): ClassificationResult;
5770+
>getClassificationsForLine : (text: string, lexState: EndOfLineState, syntacticClassifierAbsent: boolean) => ClassificationResult
57525771
>text : string
57535772
>lexState : EndOfLineState
57545773
>EndOfLineState : EndOfLineState

Diff for: ‎tests/baselines/reference/APISample_transform.js

+20-1
Original file line numberDiff line numberDiff line change
@@ -1797,7 +1797,26 @@ declare module "typescript" {
17971797
classification: TokenClass;
17981798
}
17991799
interface Classifier {
1800-
getClassificationsForLine(text: string, lexState: EndOfLineState, syntacticClassifierAbsent?: boolean): ClassificationResult;
1800+
/**
1801+
* Gives lexical classifications of tokens on a line without any syntactic context.
1802+
* For instance, a token consisting of the text 'string' can be either an identifier
1803+
* named 'string' or the keyword 'string', however, because this classifier is not aware,
1804+
* it relies on certain heuristics to give acceptable results. For classifications where
1805+
* speed trumps accuracy, this function is preferable; however, for true accuracy, the
1806+
* syntactic classifier is ideal. In fact, in certain editing scenarios, combining the
1807+
* lexical, syntactic, and semantic classifiers may issue the best user experience.
1808+
*
1809+
* @param text The text of a line to classify.
1810+
* @param lexState The state of the lexical classifier at the end of the previous line.
1811+
* @param syntacticClassifierAbsent Whether the client is *not* using a syntactic classifier.
1812+
* If there is no syntactic classifier (syntacticClassifierAbsent=true),
1813+
* certain heuristics may be used in its place; however, if there is a
1814+
* syntactic classifier (syntacticClassifierAbsent=false), certain
1815+
* classifications which may be incorrectly categorized will be given
1816+
* back as Identifiers in order to allow the syntactic classifier to
1817+
* subsume the classification.
1818+
*/
1819+
getClassificationsForLine(text: string, lexState: EndOfLineState, syntacticClassifierAbsent: boolean): ClassificationResult;
18011820
}
18021821
/**
18031822
* The document registry represents a store of SourceFile objects that can be shared between

Diff for: ‎tests/baselines/reference/APISample_transform.types

+21-2
Original file line numberDiff line numberDiff line change
@@ -5699,8 +5699,27 @@ declare module "typescript" {
56995699
interface Classifier {
57005700
>Classifier : Classifier
57015701

5702-
getClassificationsForLine(text: string, lexState: EndOfLineState, syntacticClassifierAbsent?: boolean): ClassificationResult;
5703-
>getClassificationsForLine : (text: string, lexState: EndOfLineState, syntacticClassifierAbsent?: boolean) => ClassificationResult
5702+
/**
5703+
* Gives lexical classifications of tokens on a line without any syntactic context.
5704+
* For instance, a token consisting of the text 'string' can be either an identifier
5705+
* named 'string' or the keyword 'string', however, because this classifier is not aware,
5706+
* it relies on certain heuristics to give acceptable results. For classifications where
5707+
* speed trumps accuracy, this function is preferable; however, for true accuracy, the
5708+
* syntactic classifier is ideal. In fact, in certain editing scenarios, combining the
5709+
* lexical, syntactic, and semantic classifiers may issue the best user experience.
5710+
*
5711+
* @param text The text of a line to classify.
5712+
* @param lexState The state of the lexical classifier at the end of the previous line.
5713+
* @param syntacticClassifierAbsent Whether the client is *not* using a syntactic classifier.
5714+
* If there is no syntactic classifier (syntacticClassifierAbsent=true),
5715+
* certain heuristics may be used in its place; however, if there is a
5716+
* syntactic classifier (syntacticClassifierAbsent=false), certain
5717+
* classifications which may be incorrectly categorized will be given
5718+
* back as Identifiers in order to allow the syntactic classifier to
5719+
* subsume the classification.
5720+
*/
5721+
getClassificationsForLine(text: string, lexState: EndOfLineState, syntacticClassifierAbsent: boolean): ClassificationResult;
5722+
>getClassificationsForLine : (text: string, lexState: EndOfLineState, syntacticClassifierAbsent: boolean) => ClassificationResult
57045723
>text : string
57055724
>lexState : EndOfLineState
57065725
>EndOfLineState : EndOfLineState

Diff for: ‎tests/baselines/reference/APISample_watcher.js

+20-1
Original file line numberDiff line numberDiff line change
@@ -1834,7 +1834,26 @@ declare module "typescript" {
18341834
classification: TokenClass;
18351835
}
18361836
interface Classifier {
1837-
getClassificationsForLine(text: string, lexState: EndOfLineState, syntacticClassifierAbsent?: boolean): ClassificationResult;
1837+
/**
1838+
* Gives lexical classifications of tokens on a line without any syntactic context.
1839+
* For instance, a token consisting of the text 'string' can be either an identifier
1840+
* named 'string' or the keyword 'string', however, because this classifier is not aware,
1841+
* it relies on certain heuristics to give acceptable results. For classifications where
1842+
* speed trumps accuracy, this function is preferable; however, for true accuracy, the
1843+
* syntactic classifier is ideal. In fact, in certain editing scenarios, combining the
1844+
* lexical, syntactic, and semantic classifiers may issue the best user experience.
1845+
*
1846+
* @param text The text of a line to classify.
1847+
* @param lexState The state of the lexical classifier at the end of the previous line.
1848+
* @param syntacticClassifierAbsent Whether the client is *not* using a syntactic classifier.
1849+
* If there is no syntactic classifier (syntacticClassifierAbsent=true),
1850+
* certain heuristics may be used in its place; however, if there is a
1851+
* syntactic classifier (syntacticClassifierAbsent=false), certain
1852+
* classifications which may be incorrectly categorized will be given
1853+
* back as Identifiers in order to allow the syntactic classifier to
1854+
* subsume the classification.
1855+
*/
1856+
getClassificationsForLine(text: string, lexState: EndOfLineState, syntacticClassifierAbsent: boolean): ClassificationResult;
18381857
}
18391858
/**
18401859
* The document registry represents a store of SourceFile objects that can be shared between

Diff for: ‎tests/baselines/reference/APISample_watcher.types

+21-2
Original file line numberDiff line numberDiff line change
@@ -5872,8 +5872,27 @@ declare module "typescript" {
58725872
interface Classifier {
58735873
>Classifier : Classifier
58745874

5875-
getClassificationsForLine(text: string, lexState: EndOfLineState, syntacticClassifierAbsent?: boolean): ClassificationResult;
5876-
>getClassificationsForLine : (text: string, lexState: EndOfLineState, syntacticClassifierAbsent?: boolean) => ClassificationResult
5875+
/**
5876+
* Gives lexical classifications of tokens on a line without any syntactic context.
5877+
* For instance, a token consisting of the text 'string' can be either an identifier
5878+
* named 'string' or the keyword 'string', however, because this classifier is not aware,
5879+
* it relies on certain heuristics to give acceptable results. For classifications where
5880+
* speed trumps accuracy, this function is preferable; however, for true accuracy, the
5881+
* syntactic classifier is ideal. In fact, in certain editing scenarios, combining the
5882+
* lexical, syntactic, and semantic classifiers may issue the best user experience.
5883+
*
5884+
* @param text The text of a line to classify.
5885+
* @param lexState The state of the lexical classifier at the end of the previous line.
5886+
* @param syntacticClassifierAbsent Whether the client is *not* using a syntactic classifier.
5887+
* If there is no syntactic classifier (syntacticClassifierAbsent=true),
5888+
* certain heuristics may be used in its place; however, if there is a
5889+
* syntactic classifier (syntacticClassifierAbsent=false), certain
5890+
* classifications which may be incorrectly categorized will be given
5891+
* back as Identifiers in order to allow the syntactic classifier to
5892+
* subsume the classification.
5893+
*/
5894+
getClassificationsForLine(text: string, lexState: EndOfLineState, syntacticClassifierAbsent: boolean): ClassificationResult;
5895+
>getClassificationsForLine : (text: string, lexState: EndOfLineState, syntacticClassifierAbsent: boolean) => ClassificationResult
58775896
>text : string
58785897
>lexState : EndOfLineState
58795898
>EndOfLineState : EndOfLineState

0 commit comments

Comments
 (0)