2 commits

Author	SHA1	Message	Date
Tim Neutkens	f260328900	BREAKING CHANGE: Enable newNextLinkBehavior (#41459) ... - Enable newNextLinkBehavior. See #36436 - Run next/link codemod on test suite Note that from when this lands on apps trying canary will need to run the new-link codemod in order to upgrade. Ideally we have to detect `<a>` while rendering the new link and warn for it. Co-authored-by: Steven <steven@ceriously.com>	2022-10-17 21:20:28 -04:00
JJ Kasper	32ee65efa1	Correct shallow routing behavior through history (#16477) ... When navigating from a non-shallow page to a page that was navigated to shallowly in history it causes incorrect page data to be shown since an incorrect shallow navigation is done. We can only maintain shallow routing when the current page was navigated to shallowly and the page being navigated to in history was also navigated to shallowly. Additional tests to ensure this behavior is working has also been added. Closes: https://github.com/vercel/next.js/issues/7395 Closes: https://github.com/vercel/next.js/issues/14928 Fixes: https://github.com/vercel/next.js/issues/16028	2020-08-22 21:51:14 +00:00