i verified that the actual transaction does not contain the last matching char
tr.doc.textBetween(start, end+1) will miss the triggering char at the end
add another layer of matching by introducing support for second match group
since javascript (at least in current browsers) still lacks lookbehind in regex
so now supports
/nomatch(markstart(text)markend)nomatch/ and still supports the
/markstart(text)markend/ syntax
all `nomatch` will be kept as is so kindof simulating lookbehinds
fmt(tiptap-commands): Fix all ESLint violations with `--fix`
fmt(tiptap-commands): Ignore some ESLint rules on code copied from prosemirror.
fmt(tiptap): Apply ESLint autofix to `tiptap` package sources.
fmt(tiptap-extensions): Fix ESlint violations from `marks`
refactor(tiptap-extensions): Fix ESLint violations for `plugins/Suggestions.js`.
Some of the violations required a bit of restructuring of the code/logic
fmt(tiptap-utils): Fix ESLint violations.
feat(package.json): Add yarn script to lint source code before compiling the examples.
