Eemeli Aro

I'm having trouble trying to imagine a real-world case where this would be an issue. When would you _really_ want a different message for `1.0` compared to `1.000`, and what...

I don't think that example really works? Or maybe I'm just missing something, because I can't figure out why you'd have a [1] case if it wasn't supposed to capture...

Maybe we're coming at this with different presumptions about what sort of thing @stasm's original `$num` or @Pike's `$distance` are? My baseline expectation is that those are numbers, such that...

@damianopetrungaro I'm afraid I don't really have the bandwidth available for this atm.

@vankop The situation here isn't that clear-cut. The page you linked to really only applies to a `package.json` file that's at the top level of an npm-published package. The usage...

@vankop Should this issue be reopened, or are you filing a separate issue for the planned change?

As noted in #2471, once this is implemented, the relevant notification ought to also be updated.

Yes, that looks like a python-fluent bug. According to the [spec](https://github.com/projectfluent/fluent/blob/master/spec/fluent.ebnf), only spaces are included in `blank_inline`, and effectively tabs should be considered here as `inline_text`, i.e. a part of...

I'm a bit concerned that these ratio graphs would end up hiding valuable absolute-value data. It should be relatively straightforward to validate from actual data assumptions about e.g. the effect...

The current use of `commentTabRef.current._reactInternalFiber.index` was introduced in #1676, and should be replaced with an approach that uses public interfaces only.