v0.0.21

• Handle accessors separately so as to correctly tokenize method with name get/set. Fixes #458
• Fixes unnecessary indirection of single line comment which also fixes how the new line is handled. Fixes #459 and #460

v0.0.20

• Let the new expression end if its a function expression start
• Mark TSX Class Tags Differently from Normal Html Elements. Adds an extra marker for tsx tags that are likly a javascript/typescript class instead of a standard html element. Fixes #415
• Fix the cast expression detection logic to include few more expression locations that would be operator location. Fixes #450
• End type parameter regex only on '>'. Fixes #452
• Handle NonNullOperator with arrow function. Fixes #453
• Handle single line comments so that they consume end of the line so that we dont use wrong lookup to determine end of syntax matching. Fixes #455
• Update the vsclassification for jsx attribute names to use XML Attribute since thats what jsx files used in VS 2015

v0.0.19: Scope out interface, class and alias name so as to distinuish them

• Scope out interface, class and alias name so as to distinguish them. Fixes #423 and #412
• Don't treat async on its own as arrow/function expression start. Fixes #441
• Update jsdoc regex to atom/language-javascript@70a6c53. Fixes #445 and #435
• Add scope meta.function-call for function-method calls. Fixes #413
• Handle | and & type operators such that they can handle new lines better. With this change spaces followed by this operator will be consumed and that will help not tripping end of type regex in many scenarios. We also handle { followed by these operators to handle constituent object type. Fixes #421
• Fix the regex look up to not valid if it is followed by ). Fixes #444
• Fix the type parameter regex to handle incorrect closing when arrow is present. Fixes #430
• Handle namespace declaration blocks. Fixes #433
• Update the node version for auto tests
• Add special handling of arrow function end to be start of another declaration. This helps in error recovery scenario when arrow is detected instead of function parameters on new line. Fixes #428
• Handle numeric object literal keys. Fixes #417 and #420
• Modify the rest operator detection in arrow function given that there exists spread operator now. Fixes #431
• Update the keyword to be recognized only if they are not followed by .. Fixes #418
• Handle '|' and '&' operator in function return type when they are followed by object type. Fixes #427
• Treat only expression like <Identifier> on new line as cast expression. Fixes #434

v0.0.18

• Rename scope string.regex to string.regexp. Fixes #409
• Mark object type as keyword
• Do not scope support.module.node . Fixes #408
• Update grammar for type parameter defaults that get introduces in microsoft/TypeScript#13487

v0.0.17

• Add missing type annotation pattern matching for constant like variable declarations. Fixes #407
• Handle case when function declaration is multiple lines with parameters on new line. This makes it treated like arrow, so allow arrow matching to stop when function block starts. Fixes #405

v0.0.16

• Fix the incorrectly detected arrow function type parameters which could be just relational operations. Fixes #403
• Fix the incorrect detection of arrow when it would be function call. Fixes #403

v0.0.15

• Scope the complete function call instead of just method/function call to make sure they dont get confused with arrows. Fixes #397
• Update the return type end regex. Fixes #398
• Arrow lookup is ok if it is not followed by "]" because then it has to be function call. Fixes #402

v0.0.14

• Remove the incorrect identification of function type. Fixes #387
• End arrow return type matching after we encounter arrow. Fixes #388
• Do not allow function expression to end with line break. Fixes #389 and #394
• Fix the interface/class declaration detection. Fixes #391
• Fix the precedence of literal matching so as to not mix up arrow and function call detection. Fixes #393
• Match yield while matching expression operators instead of during control statements. Fixes #396

v0.0.13: Treat the end of line as end of function declaration

• Fix arrow function determination logic to accommodate => present on next line. Fixes #383
• debugger needs to be highlighted as keyword
• Treat the end of line as end of function declaration. Fixes #384

v0.0.12: Fix the variable initializer such that new lines are handled better.

• Add support for for await of
• / followed by parenthesized expression is arithmetic division instead of start of regexp. Fixes #377
• Do not treat namespace as namespace declaration if it doesnt follow with the name. Fixes #380
• Handle the end of the new expression as look ahead of } as it can be possible in case of template expressions. Fixes #381
• Treat the { in the class body as decl block. Fixes #379 and #382 But this results in incorrect picking up of object literal in field initializer where object literal starts on new line
• Fix the variable initializer such that new lines are handled better. If the expression starts on same line use end of line to end the scope. Otherwise do not use end of line as end of scope unless its complete blank line