Support pre-release versions in expiring-todo-comments rule

[lubien]

Fixes #432

Refactor tryToCoerceVersion

Don't coerce valid semver tags on expiring-todo-comments.

I'm not sure where to test this. Should I export (exports.tryToCoerceVersion) the function and test along with the rule itself (test/expiring-todo-comments.js)? @sindresorhus any idea?

[sindresorhus]

Can you update the docs to explicitly show that prerelease versions are supported?

[sindresorhus]

I would use a fixture instead. Integration tests are usually better. Like the one in the issue:

// package.json
{ "version": "1.0.0-beta.1" }

// my-file.js
// TODO [>=1.0.0] Something must be removed

[lubien]

Sure I can do it later today.

Just be clear I'd have to create a fixture repo and put on test/integration/test.js like the others right?

[sindresorhus]

I was thinking: Publish an empty package with a prerelease version, add it as a dev dependency here, and just add another test here:

eslint-plugin-unicorn/test/expiring-todo-comments.js

Lines 222 to 225 in 1bc47a0

	{
	code: '// TODO [read-pkg-up@>=5.1.1]: when `read-pkg-up` version is >= 5.1.1',
	errors: [versionMatchesError('read-pkg-up >= 5.1.1', 'when `read-pkg-up` version is >= 5.1.1')]
	},

[fisker]

Is it possible to mock one during test?

[lubien]

Personally I haven't heard anything of sort. Tho for me this is pretty much all I need since I could handle all known cases so far.