Jan Amann

@suchipi I think you're right. After a first prototype we should be able to figure out how obtrusive this is and think of configuration options then. I've been using my...

Alright. I just had another observation. I'm currently building a React component that looks like this: ```js export default class GroupedStateProvider extends Component { static propTypes = { onSave: PropTypes.func.isRequired,...

@j-f1 Seems like [`doctrine`](https://github.com/eslint/doctrine), the JSDoc parser you mentioned above, [is no longer maintained](https://eslint.org/blog/2018/11/jsdoc-end-of-life). However @gum3n recently [implemented a Prettier plugin to format JSDoc](https://github.com/prettier/prettier/issues/5659#issuecomment-589988440) which is based on a private...

@smozely Yep, that's closely related I think. I've updated the issue description above and would aim to support this use case as well with the proposed feature.

@smozely I've had time to look into a proof-of-concept and I think the approach outlined above works remarkably well! Docs need to be written and adapted yet, but I think...

@ScreamZ Feel free to try out the pre-release and let me know if this works well for you!

@branislavbrincko In the Pages Router you should be able to assign the `locale` prop of `NextIntlClientProvider` in `_app.tsx` (see [the getting started docs](https://next-intl-docs.vercel.app/docs/getting-started/pages-router)). And yes, `i18n.ts`/`getRequestConfig` is only relevant for...

Hi and thanks for the careful analysis! I ran the performance test that's mentioned in David Reess' blog article and on my 2019 MBP I see that the formatting takes...

Possibly related to https://github.com/amannn/next-intl/issues/255, maybe also https://github.com/amannn/next-intl/issues/663.

Closing as stale …