v0.1.3

What's Changed

• #49 limit concurrency by @PanAeon in #50
• fix: allow extensions to be undefined by @so1ve in #48

v0.1.1

breaking changes:

• removed '-t' option, now testcases should be specified without it. My bad
• remove '--scope' option from vscode-tmgrammar-test. Unit tests got scope information from their header so it wasn't doing anything
• option --validate is removed
• node 10.x is no longer supported

new features:

• Now tests read grammar metadata from package.json by default. This means that if there are contributes.languages and contributes.grammars extension points in the package.json no additional configuration from command line options are necessary
• Now comment lines which not start with assertions are treated as the rest of the source code. Fixed #20
• Added scope injections. Fixed #29
• README.md and examples are updated

v0.0.11

• Bump vscode-textmate version to 5.4.0, big thanks to @isao-takejib for this.
• Fix #18 (invalid pattern in look-behind error)

NOTE: with updated oniguruma the behavior with Unicode symbols has somehow changed, but it seems to be consistent with that of VSCode

v0.0.10

• add +AllowMiddleLineAssertions flag for unit tests, which should help with languages dependent on indentation
• add functional tests to quickly check that cli is not broken

v0.0.9

• Allow split ^
• Show error messages when assertion is invalid, instead of silently ignoring the error

0.0.8

• Allow to specify multiple grammar files via command line options

0.0.7

• Fix #4 "Updating snapshots and then re-running the snapshot tests fail".
  In a nutshell, the program will try to handle both windows and unix line endings on both platforms. This will ensure that the code written in one system doesn't cause any problems on the other, and I think it's consistent with how modern text editors handle files.
• Fix incorrect reporting of program version

vscode-tmgrammar-test 0.0.6

Fix #1 "vscode-tmgrammar-snap doesn't run test cases on Windows"

Big kudos for @fachammer