You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Nest controllers now get called on client-side navigations. Now this changes everything. Previously when (re)loading the page for the first time a Nest controller would get called. Later when you clicked a link in the browser an internal /_next/ endpoint would get called to invoke getServerSideProps function and recieve its results given the arguments (e.g. path params). Now when you click the link the actual path gets fetched.
Describe the bug
When using next router's push, the nest controller does not execute.
Expected behavior
When the URL is changed through the router, as shown in the attached image, the controller does not execute. Is there a possible solution to this
Version
The text was updated successfully, but these errors were encountered: