Asynchronous JSON.stringify

Question

If I have:

fetched_user.settings = null;
fetched_user.settings = JSON.stringify(settings);
$http.post('/api_endpoint', {
  val: fetched_user.settings
});

And JSON.stringify takes forever to execute, then my understanding is val: fetched_user.settings will likely be null since this is executed asynchronously (async newbie checkpoint: is this correct?).

Normally in these situations I would supply a callback function to be executed on completion of the long-running task, however, JSON.stringify() doesn't provide the option for a callback.

How should I write this?

Why would you want it to be async? Are user setting that big? — Nathaniel Johnson
– Nathaniel Johnson, Commented Jan 4, 2014 at 3:00
If you want it to be async, use web workers or setTimeout. — Qantas 94 Heavy
– Qantas 94 Heavy, Commented Jan 4, 2014 at 3:10
Nope, settings aren't big right now. But if it were async and I relied on the fact that it executed quickly while small, then should it ever take much longer to execute it would be a tricky bug to track down. — max
– max, Commented Jan 4, 2014 at 3:39
Async APIs usually either have a callback function passed as a parameter, or return a Promise. In either case, they wouldn't have a value ever directly available via the function return. So, it wouldn't work only some times. — WiredPrairie
– WiredPrairie, Commented Jan 4, 2014 at 13:21

Robert Levy · Accepted Answer · 2014-01-04 02:55:55Z

6

JSON.stringify is not asynchronous so the $http.post line won't execute until stringification is done.

answered Jan 4, 2014 at 2:55

Robert Levy

29.1k6 gold badges66 silver badges96 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Asynchronous JSON.stringify

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related