Tristan Chin

> > Nice, can you do a pull request please? > > I was going to until I found out someone already done it #5291 The PR was closed with...

> I confirm the same thing here, example : > >  > > Do you this can be fixed ? Would be...

Just ran into this issue. Can't reproduce it but it does seem to be while using the editor the above comment talks about. About 90% of the time it works...

I'm new to `next-intl`, but I don't see where the use of `next-intl/link` is documented? I thought we had to create our own with `createLocalizedPathnamesNavigation` and `createSharedPathnamesNavigation` from the `next-intl/navigation`...

I had a similar issue and fixed it. Make sure you're not displaying zero-width characters, commonly found in preview deployments with stega encoded data from a CMS like Sanity. In...

In my case (and probably most of you too if you've followed Sanity's setup for NextJS), the issue is that I read these variables from the environment. ```ts import {...

After finally digging into alternate links, it does indeed do what I thought it would: every path gets an alternate link for each locale. This is problematic in our case,...

Yeah I agree with you, there could be risks associated with accepting `null` as a path's locale. After building our own workaround for this issue, we don't have something that...

As a workaround, you could try to use `select` instead of `body[$locale]` ```ts export const testQuery = groq` *[_type == "localizedDocument"][0] { "body": select( $locale == "en" => body.en, $locale...