tobey
tobey
That PR is looking good. It would be interesting if the project that consumes wp_mock can require php-stubs/wordpress-stubs that matches their WP version. I am not familiar enough to know...
We could run https://github.com/rectorphp/rector to automate a lot of what you're suggesting
Both. You can run it once or part of CI pipelines. In my opinion the size of a codebase should not be a factor in deciding whether to use tooling...
https://github.com/vercel/platforms/issues/174
``` export async function AppMiddleware(req: NextRequest) { ... if (redirectStrategy === 'always' || notFoundStrategy === 'multisite') { const source = await fetchSource(pathname, sourceUrl || ''); // rename from fetchRedirect if...
That is fine with me
Storybook 7 has zero config support for Next.js so should be quite easy https://storybook.js.org/blog/integrate-nextjs-and-storybook-automatically/
I just ran into this issue as well.