JJ Kasper 89ca0d10d4 Update to use getDataHref in fetchNextData (#14667) ... This updates `fetchNextData` to re-use the `getDataHref` function from `page-loader` which has more verbose handling to ensure the correct `/_next/data` URL is built. Re-using this logic ensures the `/_next/data` URL can still be built even when a mismatching `href` and `as` value is provided to `next/link`. This also fixes a case in `getDataHref` where optional values that weren't provided would fail to build the data href since the check requiring the param be present while interpolating the route values hasn't been updated to allow missing params for optional values. An additional test case has been added to the prerender suite to ensure the `/_next/data` URL is built correctly when mismatching `href` and `as` values are provided x-ref: https://github.com/vercel/next.js/discussions/14536 x-ref: https://github.com/vercel/next.js/discussions/9081#discussioncomment-31160 Closes: https://github.com/vercel/next.js/issues/14668		2020-06-29 15:14:45 +00:00
..
fixtures	Upgrade to Prettier 2 (#13061)	2020-05-18 15:24:37 -04:00
test	Update to use getDataHref in fetchNextData (#14667)	2020-06-29 15:14:45 +00:00