new(ish) html api

[TomWoodward]

we're migrating our project off the old FormatHTMLMessage component and I'm realizing that the new suggested approach for html (or any formatting) in the message relies on supporting code in the implementation. This doesn't seem to handle the common possibility of different formatting per language.

for us having links with different href, or event different text formatting, is a basic use case.

is there a way to handle this in the new api?

[longlho]

One of our options is ignoreTag that allows you to turn off HTML parsing

[TomWoodward]

thank you for the update. looking at your change i think i actually would have been fine already, but the imperative api formatMessage documented here https://formatjs.io/docs/react-intl/api#usage doesn't say it takes options, so i didn't think i could do that

[longlho]

It does in the TypeScript definition. I just need to update the docs.

[TomWoodward]

@longlho something is strange here... if i step through the types definitions i see the formatMessage definition that takes the options as the third argument, but the built javascript file here node_modules/react-intl/src/components/provider.js has:

var formatMessage = function (config, formatters, descriptor, rawValues) {
    var values = assignUniqueKeysToFormatXMLElementFnArgument(rawValues);
    var chunks = intl_1.formatMessage(config, formatters, descriptor, values);
    if (Array.isArray(chunks)) {
        return React.Children.toArray(chunks);
    }
    return chunks;
};

the first two args are bound in, leaving only two arguments for the function. I think maybe the js needs to be rebuilt?

[longlho]

oh I forgot to update that. Just released a new version that should fix that.

[TomWoodward]

ok this seems to be working now, thank you very much for your help