Question

My theory might be a bit weak asking this, so feel free to let me know.

This code is part of a browser plugin using Kango framework. Basically I have code that generates a random string that’s a userID. I also have another function that sets up a big ole JSON. It looks something like this:

function createJSON() {
data = {};
data["userID"] = generateID();
}

function generateID() {
kango.invokeAsync('kango.storage.getItem', 'userID', function(data) {
    uid = data;

    if (!uid) {
      console.log("uid doesn't exist, creating uid!");
      kango.invokeAsync('kango.storage.setItem', userID, function(data) { return data; });
    } else {
      console.log("uid found!: " + uid);
      return uid;
    }

    return data;
  });
}

kango.invokeAsync docs are here. My understanding is it works a bit like an async ajax call and in that sense it doesn’t return just in time for when I’m trying to assign its value to data[“userID”].

I think I can solve this by doing doing the userID call first and then using it’s callback(a bit vague on the terminology here) to go ahead and add to the data array.

I have no clue if that’s the right way to do it though. How do I get a return of an async function to work with?

Answer 1

You can’t do it like this because of the async nature of generateID(). It will return BEFORE the async call has finished, thus the data is not available:

data["userID"] = generateID();

Instead, you have to use a callback like this:

generateID(function(val) {data["userID"] = val;});

function generateID(callback) {
kango.invokeAsync('kango.storage.getItem', 'userID', function(data) {
    uid = data;

    if (!uid) {
      console.log("uid doesn't exist, creating uid!");
      kango.invokeAsync('kango.storage.setItem', userID, function(data) { callback(data); });
    } else {
      console.log("uid found!: " + uid);
      callback(uid);
    }

  });
}

When using asynchronous functions, you CANNOT use normal sequential programming. Instead, you have to continue your execution flow in the completion callback because ONLY then is the result of the async function known.

Thus, you won’t be able to call createJSON() and return the desired value from that. If any code after createJSON() needs the results, it also has to be in a callback.