Promise in context.dispatch about fluxible HOT 4 CLOSED

Are you using fetchr with the fetchr plugin to register your services?

from fluxible.

No, I am just trying to use a generic service that returns a promise.

from fluxible.

If the server does send a response, but with an empty state, it may be a problem with the contexts you are using. If it doesn't send any response, I'd check why the done() function is never called (something should tell the router "ok I'm done, now serve the response").

I've been fighting with both cases until I got how fluxible works. Trying to isolate the problem did help a lot!

from fluxible.

I figured it out. Basically I was using the flux-routr plugin and firing off my route dependent actions to load the initial data-

 campaigns: {
        path: '/campaigns',
        method: 'get',
        page: 'campaigns',
        label: 'Campaigns',
        action: function( context, payload, done ) {
            loadCampaigns(context,payload,done);
            done();
        }
    },

But I was calling done instead of letting loadCampaigns call done(). Therefore, the action was immediately returning and react was rendering the view assuming no changes were emitted.

 campaigns: {
        path: '/campaigns',
        method: 'get',
        page: 'campaigns',
        label: 'Campaigns',
        action: function( context, payload, done ) {
            loadCampaigns(context,payload,done);
        }
    },

Removing the done() fixed the problem.

from fluxible.