feat: Add auto completion to timeZone in the Next 13 RSC branch

[AhmedBaset]

The same as #359 but for a different branch

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
example-next-13-next-auth	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 29, 2023 6:21pm
next-intl-example-next-13	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 29, 2023 6:21pm

[vercel]

@A7med3bdulBaset is attempting to deploy a commit to the next-intl Team on Vercel.

A member of the Team first needs to authorize it.

[amannn]

Sorry, I think there's been some misunderstanding. What I meant in #359 (comment) is, that the RSC branch has some further usage of timeZone (e.g. in the i18n.ts config file). The branch adds new code in the packages/next-intl folder that uses the time zone as well—that was what I'm referring to.

We can get your changes from #359 into the RSC branch by rebasing, I just quickly did that.

However, I now saw that all the usage of timeZone in the branch automatically infer the new TimeZone type you've introduced due to shared types, so practically there's in fact nothing to do.

I should have been more precise and should have probably checked before, sorry for the confusion!

Thanks again for your help @A7med3bdulBaset!

[AhmedBaset]

However, I now saw that all the usage of timeZone in the branch automatically infer the new TimeZone type you've introduced due to shared types, so practically there's in fact nothing to do.

That what I noticed.
You can close the PR

[AhmedBaset]

Can you take a look at #365

[amannn]

Yep, I have it on my list, quite busy with work these days!