Jan Amann

Thanks for the fast reply! I did a bit more research and I found some related issues (seems like my concern is related to the underlying API of `react-side-effect`): -...

@rheaditi I tested a few different approaches and ended up with this resolver for a file upload with `[email protected]`. ```js import FormData from 'form-data'; import {GraphQLUpload} from 'apollo-upload-server'; import rawBody...

> To get around this, we previously had to store the file to the fs temporarily & create a readstream from the fs file and this helps us completely avoid...

@gregory Yep, that's true. Ideally we'd just forward the stream to `form-data`, but as mentioned above in my code comment, there's a bug that prevents this currently. My solution is...

I've published an adapter for Next.js: [`next-query-params`](https://github.com/amannn/next-query-params) It was originally based on the code that is discussed in this issue but also contains a few bugfixes that popped up over...

A note for the people following along here: I've just published [`[email protected]`](https://github.com/amannn/next-query-params/blob/main/CHANGELOG.md#400-2022-08-30) which is based on `use-query-params@2` and the introduced concept of adapters. This removes the necessity for a wrapper...

Possibly another instance of https://github.com/amannn/next-intl/issues/255, it's unclear to me if there's anything `next-intl` can do here. This might be something that needs to be addressed upstream in Next.js.

I'll close this issue, since other message formats are currently not planned.

Merging messages from another locale as a fallback is absolutely fine and also mentioned in [the messages docs](https://next-intl-docs.vercel.app/docs/configuration#messages) ("How can I use messages from another locale as fallbacks?").

@philipbjorge Have you considered using [select](https://next-intl-docs.vercel.app/docs/usage/messages#selecting-enum-based-values) for this use case? ``` "state": "{state, select, WA {Washington} OR {Oregon} other {{state}}" ```