Closed Bug 1564268 Opened 7 years ago Closed 6 years ago

Create a FluentResourceSource to load Fluent files from Remote Settings

Categories

(Core :: Internationalization, enhancement, P3)

enhancement

Tracking

()

RESOLVED FIXED

People

(Reporter: Pike, Unassigned)

References

(Blocks 1 open bug)

Details

For user journey, we want to be able to load Fluent strings from Remote Settings.

There's a few things we should figure out:

For one, what's the public interface that a source should have for the l10n registry.

The other is, what should happen on sync events on remote settings. For this we have a couple of options:

  • update content on restart
  • update content on reload
  • update existing content

The latter might be surprising to users, but the first two are really close.

Nan, are the bugs we should hook this up to for Skyline?

Pike, thanks for kicking this off!

The other is, what should happen on sync events on remote settings. For this we have a couple of options:
The latter might be surprising to users, but the first two are really close.

Agreed, we're inclined to take any of the first two strategy for now.

Nan, are the bugs we should hook this up to for Skyline?

Yes, we have filed following bugs on our end,

  • Bug 1564187 - The meta bug for User Journey to achieve the off-train message localization.
  • Bug 1564189 - Preps in the Remote Settings infrastructure (creating RS collection, permission setup etc), those are all server side tasks, no client side change needed at the moment for RS.
  • Bug 1564194 - Interface between l10n and Remote Settings so that we can publish Fluent files to Remote Settings.
  • Bug 1564188 - Use remote Fluent files in the User Journey code base.

With the builtin support of FluentResourceSource for RS, we can revisit those bugs if necessary :)

Blocks: 1564188
Priority: -- → P3

Is that done now?

Flags: needinfo?(l10n)

Within the scope of this bug, yes. We haven't condensed the learnings in AS into something that'd be usable outside of it, but that's not the scope of this bug, so marking FIXED.

Status: NEW → RESOLVED
Closed: 6 years ago
Flags: needinfo?(l10n)
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.