Exact terms not always detected

[kimburgess]

Thank you for putting this rule together.

I've been using it and have run into a number of cases where exact terms are not always matched. Unfortunately I have not had time to put together a PR, but have traced it to being due to the RegExp that is built here:

textlint-rule-terminology/index.js

Lines 126 to 138 in c3f366a

	/**
	* Match exact word in the middle of the text
	* @param {string} pattern
	*/
	function getExactMatchRegExp(pattern) {
	return new RegExp(
	// 1. Beginning of the string, or any character that isn't "-" or alphanumeric
	// 2. Exact match of the pattern
	// 3. Space, ". ", "." at the end of the string, end of the string
	`(?<=^|[^-\\w])\\b${pattern}\\b(?= |\\. |\\.$|$)`,
	'ig'
	);
	}

Loading this into regex101, it's possible to see some of these cases failing: https://regex101.com/r/vOBa0O/1.

As a temporary workaround, the alternate ['regexp', 'replacement'] configuration syntax does not appear to be impacted.

[sapegin]

🎉 This issue has been resolved in version 3.0.2 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀