Barret, On Thu, Jan 18, 2024 at 11:58 AM Barret Rennie <[email protected]> wrote:
> Hi everyone! > > In H1 the Nimbus team is planning to deprecate isEarlyStartup features in > the feature manifest. The plan is to migrate every feature that uses > isEarlyStartup to use setPref for any variables that need to be read before > the Nimbus store is ready. > > This will also result in the majority of the NimbusFeatures C++ APIs being > removed. There are very few consumers of this API to migrate and all uses > can be replaced with pref reads of setPref variables. > > This work will be tracked in bug 1875331 > <https://bugzilla.mozilla.org/show_bug.cgi?id=1875331>. > Two small thoughts about this. First, `setPref` and `fallbackPref` are mutually exclusive at this time. We lose a little bit of local development and testing flexibility by not having `isEarlyStartup` and `fallbackPref` together. But the current Nimbus preference situation is so complicated and so frequently misconfigured that clean-up and focused normalization of this area is surely a good thing. Second, has there been a discussion of direct preference access vs. some Nimbus C++ API for reading that knows about `setPref`? It would be really nice to keep the Nimbus-level separate from the extremely general and hard to interrogate Gecko preferences system. That is, we lose implementation flexibility by exposing the underlying storage layer to consumers. What do we gain in return? Best, Nick -- You received this message because you are subscribed to the Google Groups "[email protected]" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/a/mozilla.org/d/msgid/dev-platform/CAMnWBR0Du-x2g_j4n5QzrX3zKt-aCixAbawWrb45g%3DmWJcOL3w%40mail.gmail.com.
