Ron Buckton
Ron Buckton
Stack trace: ``` Error: Recovery failed to advance. at Parser.parseList (C:\path\to\project\node_modules\grammarkdown\dist\parser.js:387:27) at Parser.parseNoSymbolHereAssertionTail (C:\path\to\project\node_modules\grammarkdown\dist\parser.js:478:30) at Parser.parseAssertion (C:\path\to\project\node_modules\grammarkdown\dist\parser.js:508:25) at Parser.parseSymbol (C:\path\to\project\node_modules\grammarkdown\dist\parser.js:687:25) at Parser.parseSymbolSpanRest (C:\path\to\project\node_modules\grammarkdown\dist\parser.js:709:29) at Parser.tryParseSymbolSpan (C:\path\to\project\node_modules\grammarkdown\dist\parser.js:703:25) at Parser.parseSymbolSpanRest (C:\path\to\project\node_modules\grammarkdown\dist\parser.js:710:27) at...
`ecmarkup` has a few lint rules that grammarkdown doesn't enforce on its own, but that make sense: - `[empty]` assertions should have no other content: https://github.com/tc39/ecmarkup/blob/52df46d6177a14f6d101a34aecbebf5834c77571/src/lint/utils.ts#L70 - `but not` operators...
To simplify the internals of `grammarkdown`, I'm considering dropping the synchronous APIs such as `SyncHost`, `parseSync`, `bindSync`, `checkSync`, etc. However, doing so would have a significant impact on tools such...
Add support for a html report output in the grammarkdown cli: ``` grammarkdown source.grammar --format html ``` This would have the following characteristics: - Grammar emit to a `` (HTML...
### My Environment - [ ] Windows 7 or below (not truly supported due to EOL - see wiki for details) - [ ] Windows 8 - [ ] Windows...
This adds support for synonyms for tags. Fixes #203
This builds on #324 to support parsing the new DeclarationReference format in TSDoc.
This adds a number of utility methods to various pieces of `DeclarationReference` to make it easier to make changes. NOTE: API for `from()` and `with()` is inspired by the Temporal...
This depends on #204 and will remain in a Draft PR state until that PR is merged. Fixes: #235
JSDoc supports synonyms for many tags, and it would be worthwhile to support those synonyms for code bases that were previously migrated from JavaScript to TypeScript without requiring an investment...