Access current lang in getStaticProps and getStaticPaths about next-translate HOT 6 CLOSED

@aralroca
Wow, that was fast.
It works, many thanks. :)

However there's one rare case which regexp in hasSpecialMethod doesn't cover:
export async function getStaticProps() {}

from next-translate.

@maksymdukov async function syntax should work in 0.13.0-canary.2 👍

from next-translate.

I'm not sure about some hack, but I guess that is not possible, at least right now.

However, I think that we should change our way to do the build in the CLI in order to provide it, using dynamic routes with [lang]. After that, it should be possible to get the current language via params.

Thank @maksymdukov to report this! This will be very useful for 0.13.0 release 🙂

from next-translate.

When this issue will be solved vercel/next.js#11309 it will be trivial to wrap the lang to getStaticProps & getServerSideProps 🤞 Meanwhile, I'm going to investigate if there is another way to handle this!

from next-translate.

@maksymdukov from now on, the lang will be available on getStaticProps, getStaticProps and getServerSideProps.

I'm going to explain it better in the docs for 0.13.0 version. But a simple example:

export function getStaticProps({ lang }){
   return { props: { data: getDataFromLang(lang) } }
}

The 0.13.0 release will be available soon. However, I released the 0.13.0-canary.1 with that feature. Please, confirm that 0.13.0-canary.1 works in your case 👏!

https://github.com/vinissimus/next-translate/releases/tag/0.13.0-canary.1

from next-translate.

Good catch!! Thanks, this should be fixed before 0.13.0 release! Thanks!

from next-translate.