Eemeli Aro

Here's a concrete proposal for the interfaces of the formatted message parts, where the return type of a `formatToParts()` method or function would be `FormattedPart[]`: ```typescript interface FormattedDynamic { type:...

@longlho Your reference link and at least my understanding of your concerns would indicate that you might be talking about the representation of the source message, rather than this formatted...

@stasm Really good point. And I think it made me change my mind on a few things. I actually had a decently long reply to this written, but then I...

Okay, updated proposal based on comments from @longlho and @stasm. I think the parts should be a flat list `MessageFormatPart[]` where ```ts type MessageFormatPart = { source?: string } &...

> So html / tts / markdown / ansi_escapes are functions, not "bold" and "italic" and "link" I don't see how we could make this assumption. It's certainly a possible...

Having read all of the preceding, to me perhaps the most relevant question to ask in this particular thread is related to this: > The engine knows about formatToX, and...

One limitation that I think we can and should make is that the set of functions that could be called must be defined ahead of time. As in, there should...

> The reason I think it is important is that we need to early on decide whether what our target is does: > > ``` > printf("Hello, { $user }");...

Confirmed. This mostly affects the `'*'` special-case locale code. It's not just the date functions, but the locale isn't detected at all from the object path like it should be....

A PR for this would be welcome. Might make more sense to produce a d.ts file, though.