Josh Swan

The best way of achieving this at the moment would be to use a custom `renderLink` function. It receives the match as an argument, allowing you to perform custom rendering...

Definitely open to improving the experience around message identifiers. I'd prefer something a little more "automatic" though - perhaps something that works with `loadMessages`.

Yeah I think we'll just have to ignore typing the nested/string syntax as TS doesn't support it. However, the array syntax for nested keys (e.g. ['foo', 'bar']) could be strongly...

Just released your original proposal in v4.2.0. It's definitely the simplest and most flexible solution on the table. We use this library internally at my company now (which was the...

I wouldn't call it a "break" since the original string typing still applied. However, to avoid people getting their types messed up, I just released v4.2.1 which reverted the changes....

There isn't currently a locale-based fallback mechanism for `formatMessage`. That's something that I could potentially explore adding or accept a PR for, though the mechanism for deciding the fallback locale...

Sounds good, that does seem like a decent workaround for now. Per another issue that came up earlier today, a `defaultLocale` option/prop is now available. Currently it's used when the...

That's the current expected behavior, though I do agree that it may not be optimal. As I just mentioned in #59, it might be better for you to just disable...

This seems to be a shortcoming of RN or potentially the underlying platform. I did a bit of testing with the `Text` component itself, and selectable and onPress really don't...

URL matching is handled under the hood by [Autolinker.js](https://github.com/gregjacobs/Autolinker.js). From what I can tell, this is a side effect of matching URL schemes, so disabling schemeMatches fixes the issue, though...