32.0.0 (2021-02-15)
Bug Fixes
- check-examples: change default extension for simulated file name of
[@example](https://github.com/example)
frommd
tomd/*.js
. Only applies whenmatchingFileName
is not used. (2cc1227)
BREAKING CHANGES
- check-examples: Per update to
eslint-plugin-markdown
v2 and its support of ESLint 7's new processor API, fenced blocks can (and must) be targeted separately from the Markdown parent file as a whole, so in order to allow the sameoverrides
config to be reusable between Markdown fenced blocks and@example
tags (since one often wishes to disable the same kind of rules for each, being as that each may deliberately lack full context, e.g., undefined or unused variables), we update the default simulated extension set for@example
tags bycheck-examples
to simulate an expression which will now be a suitable choice foroverrides
in targeting Markdown fenced blocks using the new parser API, as with eslint-plugin-markdown@2 (i.e., "md/*.js" instead of "md").
If you need to use ESLint 6 (or eslint-plugin-markdown < 2, for example) with check-examples
, you should be able to manually supply the matchingFileName
option targeting "md", e.g., set to 'dummy.md
.
This commit also simplifies a testing example to avoid it throwing with changed config not having proper babel support (not meaningful to test anyways)