Fix for linking absolute paths in file:// scheme

Author: gregjacobs

src/parser/parse-matches.ts

@@ -239,12 +239,12 @@ export function parseMatches(text: string, args: ParseMatchesArgs): Match[] {
 
         // For debugging: search for and uncomment other "For debugging" lines
         // table.push([
-        //     charIdx,
+        //     String(charIdx),
         //     char,
         //     `10: ${char.charCodeAt(0)}\n0x: ${char.charCodeAt(0).toString(16)}\nU+${char.codePointAt(0)}`,
         //     stateMachines.map(machine => `${machine.type}${'matchType' in machine ? ` (${machine.matchType})` : ''}`).join('\n') || '(none)',
         //     stateMachines.map(machine => State[machine.state]).join('\n') || '(none)',
-        //     charIdx,
+        //     String(charIdx),
         //     stateMachines.map(m => m.startIdx).join('\n'),
         //     stateMachines.map(m => m.acceptStateReached).join('\n'),
         // ]);
@@ -382,10 +382,11 @@ export function parseMatches(text: string, args: ParseMatchesArgs): Match[] {
 
     function stateSchemeSlash2(stateMachine: StateMachine, char: string) {
         if (char === '/') {
-            // 3rd slash, must be an absolute path (path-absolute in the
-            // ABNF), such as in a file:///c:/windows/etc. See
+            // 3rd slash, must be an absolute path (`path-absolute` in the
+            // ABNF), such as in "file:///c:/windows/etc". See
             // https://tools.ietf.org/html/rfc3986#appendix-A
             stateMachine.state = State.Path;
+            stateMachine.acceptStateReached = true;
         } else if (isDomainLabelStartChar(char)) {
             // start of "authority" section - see https://tools.ietf.org/html/rfc3986#appendix-A
             stateMachine.state = State.DomainLabelChar;
@@ -1092,7 +1093,7 @@ export function excludeUnbalancedTrailingBracesAndPunctuation(matchedText: strin
 }
 
 // States for the parser
-// For debugging: temporarily remove 'const'
+// For debugging: temporarily remove `const` from `const enum`
 const enum State {
     // Scheme states
     SchemeChar = 0, // First char must be an ASCII letter. Subsequent characters can be: ALPHA / DIGIT / "+" / "-" / "."

tests/autolinker-url.spec.ts

@@ -269,10 +269,19 @@ describe('Autolinker Url Matching >', () => {
             const result = autolinker.link('file:some-file.txt mid-sentence');
 
             // TODO: in theory this is a valid url, but do we want to continue
-            // autolinking this in the future?
+            // autolinking this in the future? Seems like Autolinker may link
+            // "too much" in this case, such as "things:stuff"
             expect(result).toBe(`<a href="file:some-file.txt">file:some-file.txt</a> mid-sentence`);
         });
 
+        it('should match a file url with an absolute path', function () {
+            const result = autolinker.link('check out file:///c:/windows/etc mid-sentence');
+
+            expect(result).toBe(
+                `check out <a href="file:///c:/windows/etc">file:///c:/windows/etc</a> mid-sentence`
+            );
+        });
+
         it("should NOT autolink possible URLs with the 'javascript:' URI scheme", () => {
             const result = autolinker.link("do not link javascript:window.alert('hi') please");
             expect(result).toBe("do not link javascript:window.alert('hi') please");