Axel Hecht

As we're breaking compat, should we also move from pgkutil-style namespace packages to native ones? This would be a good time, as we could just generally bump mutual requirements on...

Some feedback along the way here. I like the general idea, and stas said so, too. I also appreciate that the performance impact in this patch is moved to actually...

> For example, in [elm-fluent](https://github.com/elm-fluent/elm-fluent) I implemented a very different approach, where essentially all errors in FTL files become compile time errors. I did this because: > > 1. You...

Also a port of https://github.com/projectfluent/fluent.js/issues/524, I'd say.

The file format is documented at https://moz-l10n-config.readthedocs.io/en/latest/fileformat.html, though there might be a few quirks. The code for compare-locales is at https://hg.mozilla.org/l10n/compare-locales, so you could wrap your own project management and...

So, for Firefox, we're using cross-channel localization, and our reference strings are at https://hg.mozilla.org/l10n/gecko-strings/. The l10n config file for Firefox in there is https://hg.mozilla.org/l10n/gecko-strings/file/default/_configs/browser.toml.

I'd probably put it in the card actions, next to https://github.com/backstage/backstage/blob/25b94e63455f1fb170506f9e84e3f430f4b79406/plugins/scaffolder/src/components/TemplateCard/TemplateCard.tsx#L210-L217. In the meantime, I started wondering if this can be implemented w/out adding a dependency on the techdocs plugin.

I'm afraid I'm pretty booked these days, sorry.

I've done some more investigation, and here's what I found: bodyParser.json checks the limit on the uncompressed stream, and it's using the 100kb default limit from express (express.json is just...

I like the idea that we'd have compile-time checks for string errors. I wonder if you could extend your ideas here for a couple of things: For one, we'll need...