Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Add info variant for logging in @actions/core

See original GitHub issue

Info:

Currently @actions/core provides debug(), error() and warning(). These do not cover the use case of logging information that you would like to always show in the logs but are not necessarily an error or warning of an issue.

Feature Request:

Add an info variant to the logging provided by @actions/core

Issue Analytics

State:
Created 4 years ago
Comments:6 (4 by maintainers)

Top GitHub Comments

3reactions

damccormcommented, Sep 4, 2019

Hm, I think as I consider this more I’m actually convinced that we should have this. Thanks for the feedback.

Ultimately, while the other logging functions do have special implementations on the runner, we’re exposing a logging interface and the author shouldn’t have to understand that distinction. Addressed in #111

0reactions

xt0rtedcommented, Sep 4, 2019

I was confused by this at first too. Once I realized what the core.debug() etc. functions did it made sense why there wasn’t one for info. It could be useful to mention this in the docs.

I’ve been considering creating my own logger that uses the methods from this package when available, and then fall back to console for the rest. That way I have a consistent logging experience.

Another option was to use console everywhere and then replace console.debug etc. with the copies from this package. This would also work better with other packages that use the console functions.