0

I have a function that gets input constantly but then only processes it every minute with a cron job.

The most recent output should be stored in a variable and retrieved from the outside at random times.

Here in a very simplified form:

let input = 'something';

let data = '';
data += input;

require('node-schedule').scheduleJob('* * * * *', somethingMore);

function somethingMore() {
let output = data += 'More';
// return output;
}

console.log(output);

Initializing the variable outside the function like above doesn't seem to work in this case.

Calling the function directly or assigning it to a variable doesn't help, as it would run it before it's due.

I also tried with buffers, but they don't seem to work either, unless I missed something.

The only thing that does work is writing a file to disk with fs and then reading from there, but I guess it's not the best of solutions.

lucian
  • 623
  • 10
  • 21

1 Answers1

1

It seems like you just let your chron function run as scheduled and you save the latest result in a module-scoped variable. Then, create another exported function that anyone else can call to get the latest result.

You're only showing pseudo-code (not your real code) so it is not clear exactly what you want to save for future inquiries to return. You will have to implement that part yourself.

So, if you just wanted to save the most recent value:

// module-scoped variable to save recent data
// you may want to call your function to initialize it when
// the module loads, otherwise it may be undefined for a little bit
// of time
let lastData;

require('node-schedule').scheduleJob('* * * * * *', () => {
     // do something that gets someData
     lastData = someData;
});

// let outside caller get the most recent data
module.exports.getLastData = function() {
    return lastData;
}
jfriend00
  • 683,504
  • 96
  • 985
  • 979
  • This: `let lastData;` / `lastData = someData;` ! Initializing with some other name and then equating (as opposed to initalizing and using directly as I did) does it, no `module.exports` needed for my use case. – lucian Feb 07 '22 at 10:28
  • @lucian - I didn't understand that last comment. Were you asking me something? – jfriend00 Feb 07 '22 at 22:27
  • @ jfriend00 – no, was just pointing out for whoever might read this in the future that just part of the solution might be enough in some cases. – lucian Feb 08 '22 at 08:08