oracc / nisaba

GNU General Public License v3.0
3 stars 0 forks source link

Logger #26

Closed raquelalegre closed 3 years ago

raquelalegre commented 3 years ago

Nammu has a logger and it was really useful specially when we were checking the communication with the server. If we can use whatever logging system VS Code has, that'd be great. Otherwise we should keep our own.

I realised about this as I was looking into the request.log returned by the server validation response, which is useless for the user but can tell us information about the server if something is not going well.

giordano commented 3 years ago

For relatively simple needs, console.log may be enough. After some research I found @vscode-logging/logger, which seems to provide more sophisticated features, including different logging levels, but it doesn't seem to be super popular, so I'm not sure it's the best option out there.

ageorgou commented 3 years ago

From a quick look I also can't see an internal VS Code logger that we can use, nor anything in the Node.js standard library.

Apart from the one @giordano mentioned, there are several Javascript/Typescript logging libraries (see e.g. this list). The most popular seem to be:

There are various tutorials and articles with examples, so trying one or two might not be too hard.

ageorgou commented 3 years ago

Opened #33 for discussing what we need and looking into the different options. I suggest we keep this issue for tracking the progress of the actual implementation.