No Error on missing Translation about eo-locale HOT 3 CLOSED

Hi @mi-roh! Thanks for the issue. You can provide custom onError handler to TranslationsProvider component as property. By default it is console.error.

from eo-locale.

@mi-roh Does it work for you? Shall I close the issue?

from eo-locale.

Hi @pret-a-porter,
not really. In my subjective view, onError is ideal to link eo-locale with your monitoring. But its not useful to prefilter messages.

We already use a custom onError for our monitoring. But there is no way to filter between the Errors passed. Beside of filter on the Error-Message-Shema and grabbing the missing id with an regex.

What I haven't mentioned in my first post. Within onError there is no way to detect if a default message was used. Even that little Information would optimize the filter options.
f.e.:
this.onError(new Error(`[eo-locale] id missing "${id}" in ${this.language}. Displayed "${message}" instead.`))

I created a fork with two commits. First adds a custom missing handler. To prevent regexing on error messages. Second passes the FormatMessageOptions down to the missing handler. Custom filters or logging messages are possible for there is now a context given.

With a wrapper and some regexing we get the job done. I don't know if I'm the only one how would like to prefilter. But I would be happy for every little improvement. Even if only something like Displayed "${message}" instead. gets added to the Error.

from eo-locale.