fix: scan full pattern when tokens are requested

The `tokens` option implicitly enables `parts`, but did not enable
full-pattern scanning. This caused scanning to stop at the first glob
and merge the remaining path segments into the final token.

Include `tokens` in `scanToEnd` and add regression coverage for #62.

Author: mrmlnc

lib/scan.js

@@ -50,7 +50,7 @@ const scan = (input, options) => {
   const opts = options || {};
 
   const length = input.length - 1;
-  const scanToEnd = opts.parts === true || opts.scanToEnd === true;
+  const scanToEnd = opts.parts === true || opts.tokens === true || opts.scanToEnd === true;
   const slashes = [];
   const tokens = [];
   const parts = [];

test/api.scan.js

@@ -375,6 +375,11 @@ describe('picomatch', () => {
       assertParts('foo/[0-9]/[0-9]', ['foo', '[0-9]', '[0-9]']);
       assertParts('foo[0-9]/bar[0-9]', ['foo[0-9]', 'bar[0-9]']);
     });
+
+    it('issue #62: should enable parts when tokens are requested', () => {
+      const state = scan('a/b/*/c', { tokens: true });
+      assert.deepStrictEqual(state.parts, ['a', 'b', '*', 'c']);
+    });
   });
 
   describe('.base (glob2base test patterns)', () => {