Andreas Loew

This behaviour is on purpose. The older versions of ngx-translate used "any" everywhere as data type. This made things hard to handle in the code. The new release adds more...

Would it not make more sense to separate the items? If it's degrees etc, it's not language dependent, I suppose. So duplicating the data would give you the risk of...

I currently have additional privileges, such as handling tickets on the project: https://github.com/orgs/ngx-translate/people. However, there isn't a formal "team" structure in place. We've never had meetings to discuss project direction,...

I've meanwhile forked the project: @codeandweb/ngx-translate @codeandweb/http-loader The current work in progress is available as a beta version on npm.

It's already available. I've released V16 of my fork last week. This migration guide explains how to switch to my fork and also explains the benefits of doing so: https://ngx-translate.org/getting-started/migration-guide/

The links on https://ngx-translate.org point to https://github.com/codeandweb/ngx-translate - my forked repo. I can't do anything here since Olivier ignores all communication and I don't have the right to change anything...

Got permissions by Olivier to publish updates here...

I switched the type to export type InterpolationParameters = Record; this ensures that we can use the string as index while also allowing objects.

Isolate means that the instance you create is completely independent from the other ones. I've inspected the code so far... isolate should work as it is. The implementation is not...

You can use the "JSON (Hash)" format to try it - it enables the polygon packer but disables some PixiJS specific things (Animation detection). The rest of the format is...