Build directory output for catch-all routes

[Timer]

Thanks for the quick response to this. Unfortunately I don't think this is fully resolved:

On 9.2.1-canary.5,

With exportTrailingSlash: true in next.config.js,

With template pages/[...slug].jsx,

export async function unstable_getStaticPaths() {
	return [{ params: { slug: ['en_CA', 'about'] } }];
}

export async function unstable_getStaticProps({ params }) {
	console.log('\nparams', params);
	const { slug } = params;
	const props = {
		props: {
			slug,
		},
	};

	return props;
}

The build works, but the nested directories created are not as (I) expected:

Note the directory named en_CA%2Fabout:

This is the build console output. Note the slug is passed to getStaticProps as a single string within an array (params { slug: [ 'en_CA/about' ] }):

What I think is expected behavior - let me know if I'm off here:

• The directory structure should be created to match the the catch-all path
• The slug value is passed either as an array of strings (as returned from getStaticPaths) OR as a single string (concatenated with /), but not a single string within an array.

Originally posted by @dpfavand in #10173 (comment)

[jamesvidler]

I can confirm this works when exportTrailingSlash is set to false.

[Timer]

Fixed via #10379

[balazsorban44]

This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.