Eemeli Aro
Eemeli Aro
Presumably this may be closed, given our current standalone/open/close function definitions?
I believe that this is somewhat out of date, and the topic is now best approached through our work on the function registry.
Closing this in favour of #386.
Closing this, as the actual bug has long since been fixed and the upstream dependency has not shown any interest in making required changes.
Closing in favour of #368.
> I work in Rust, so this may have a different answer than if I worked in JavaScript or Python (or maybe not). > [...] > I didn't know if...
@waywardmonkeys Hang tight for a short bit still? I'm chasing up some approvals within Mozilla, and that's taking a bit longer than I would've liked. The core issue from our...
It's taken an age and a half, for which I apologise, but we've finally reached [this conclusion](https://bugzilla.mozilla.org/show_bug.cgi?id=1884397) at Mozilla: > At this time we're allowing community to take over more...
Closing and pinning sounds like exactly the right move here.
This sounds like a rather good idea! Potentially not just for Fluent, but for localization file formats in general. Is the actual need more to identify FTL files specifically, or...