Initializer is now unable to run after SPA loaded?

DaleZ

In one of my extentions, I had written the code below:

app.initializers.add('flarum-msemoji', (app) => {
  // (...ignored some code)
  if (app.forum.attribute("flarum-msemoji.disable_autocomplete") != '1') addComposerAutocomplete();
});

But then I found it failed, with console I found that when it performs, app.forum is null.
I tried to search something relative, then found askvortsov, but there's nothing helpful.
I had to rewrite it into this:

  new Promise(function (resolve) {
    var id = setInterval(function () {
      if (app.forum) {
        if (app.forum.attribute) {
          clearInterval(id);
          resolve();
        }
      }
    }, 500)
  }).then(function () {
    if (app.forum.attribute("flarum-msemoji.disable_autocomplete") != '1') addComposerAutocomplete();
  });

It can work, but as you can see, it just seems too low. Is there any way to improve it?

DaleZ

The app.booted is also keeps false, too.

clarkwinkelmann

As far as I remember, initializers always run before the app boots, precisely so extensions can modify the code of core classes before they are initialized for the first time. So I would be surprised if that code worked at all before.

If you need to react to values on the app.session.user object or interact with methods of the Forum object, the solution I usually use is to hook into the page init hook, that way the code runs as the same time as Flarum starts rendering the first page, for example clarkwinkelmann/flarum-ext-follow-tags-promptblob/master/js/src/forum/openAutomaticModal.ts

But if all you need is a toggle for a feature and don't really need to interact with models or the store, or even NEEDs to trigger before that, you can do that right away by bypassing the store and reading app.data. I know I've done this in the past but can't find any extension where I use this right now. One option is to add your setting key directly to the app.data in the backend, that way it's easiest to retrieve. But if you exposed it through an attribute on the forum model, you should also be able to access the raw model payload in app.data.resources or app.data.apiDocument, but I'm not sure what the timing is and which attributes are actually available during boot.