What Should Module Logs Include? about image-sequencer HOT 8 CLOSED

from image-sequencer.

Oh. You meant it this way? I thought it was more of a success/error log. Somewhat like syslog.
I get what you are saying.

Would we also log when module options are changed, say, in the web UI?

That is a great question. Haven't thought of it but yes, I think we should.

So the Log could actually be a set of jsons which represent the user input. Basically everything what the user runs via sequencer.SOMETHING along with options and the output as well.

Also what do you think of this:

Where does the logged data go? Does it remain accessible only for that session or should it get stored in a LOG file (for Node.js)?

?

from image-sequencer.

from image-sequencer.

So something like this, right?

log = [
    {method: "addSteps", json_q: { (data goes here) }},
    {method: "run", json_q: { (data goes here) }},
    ...
];

from image-sequencer.

I have pushed a basic draft of this to ccpandhare:development

from image-sequencer.

from image-sequencer.

Well I do think that it's a bit too much... We can store it in a different object, maybe sequencer.state ?

from image-sequencer.

from image-sequencer.