feat: add full support for fuzzy linking

[robertkowalski]

this PR adds full support for fuzzy links. to keep backward
compat, the old linkify is still kept.

[robertkowalski]

@captainsafia the only difference why i kept the old linkify method for backwards compat is this behaviour:

ansi-to-react/__tests__/index.spec.tsx

Lines 134 to 147 in deb6520

	test("doesn't linkify partial matches", () => {
	const el = shallow(
	React.createElement(
	Ansi,
	{ linkify: true },
	"cant click this link: 'http://www.google.com'"
	)
	);
	expect(el).not.toBeNull();
	expect(el.text()).toBe("cant click this link: 'http://www.google.com'");
	expect(el.html()).toBe(
	"<code><span>cant click this link: &#x27;http://www.google.com&#x27;</span></code>"
	);
	});

this becomes a link with the new linkify-it method, even when fuzzylinking is turned off in the lib via options

do you think we should keep this behaviour, or can i introduce a breaking change?

[captainsafia]

@robertkowalski Thanks for getting this PR out and apologies for being a little slow on the review. I tread a little careful with this link stuff because we have had a few issues in the past with it so it requires some extra caution. 😄

[captainsafia]

Might want to rebase now that the other PR has been merged.

[robertkowalski]

rebased! :)

[captainsafia]

At the risk of avoiding too many magic booleans in this API, should we make linkify and enum that takes different values for the new vs. old behavior?

[robertkowalski]

good idea.

i wasn't able to get the typescript type "enum" working with the code without breaking backwards compat, so i extended the type for linkify

[robertkowalski]

@captainsafia using typescript enums did not work for me without breaking backwards compat... maybe i missed something, but passing the option "fuzzy" did not work for

enum E {
  true,
  false,
  "fuzzy"
}

via:

React.createElement(
  Ansi,
  { linkify: "fuzzy" },
  "this is a fuzzy link: example.com"
)

where the intention is that users from older versions still can use true/false

---

don't worry on the delay btw

PS: it would be great if you would publish a new version after the merge, i think automatic publishes are broken on master branch currently

[robertkowalski]

friendly ping @captainsafia :)