withTracker , async and subscriptionReady

3.0 migration
1

Hello,
withTracker and async seems weird

export const PageLayoutContainer = withTracker(({}) => {
    const logContext = "PageLayoutContainer";
//  console.log(logContext, "subscribe('translations')")
    let subscriptionTranslations = Meteor.subscribe('translations');
let user ;
//    user =  await Meteor.userAsync();
     let result = {
        subscriptionReady: subscriptionTranslations.ready(),
        user: user
    };
    return result;
})(PageLayout)

→ we dont have the user as it is in a async method but the update is passed to PageLayout and the subscriptionReady becomes true at some point.

I switched to async method in the withTracker to get the user, the result is not more updated (subscriptionReady is never changed) but we have the user


export const PageLayoutContainer = withTracker(async ({}) => {
    const logContext = "PageLayoutContainer";
//  console.log(logContext, "subscribe('translations')")
    let subscriptionTranslations = Meteor.subscribe('translations');
let user ;
  user =  await Meteor.userAsync();
     let result = {
        subscriptionReady: subscriptionTranslations.ready(),
        user: user
    };
    return result;
})(PageLayout)

Did I miss something ?

2

On the client side, you can use Meteor.user(). If you do that, you can change async ({}) => to just ({}) =>

3

oh yes sure, this is a bad example for the real question : what about any other async function that get results from mongodb in with tracker ?
Should duplicate all common code client and server for one version async and the other sync ?

4

Generally speaking, you’ll want to be using suspense boundaries and the suspense enabled versions of hooks from meteor/react-meteor-data/suspense