-
-
Notifications
You must be signed in to change notification settings - Fork 128
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Logging provider #371
Comments
This issue is stale because it has been open for 30 days with no activity. |
This issue is stale because it has been open for 30 days with no activity. |
Still on my list |
This issue is stale because it has been open for 30 days with no activity. |
This issue was closed because it has been inactive for 14 days since being marked as stale. |
s1hofmann
added a commit
that referenced
this issue
Sep 14, 2022
s1hofmann
added a commit
that referenced
this issue
Sep 14, 2022
s1hofmann
added a commit
that referenced
this issue
Sep 14, 2022
s1hofmann
added a commit
that referenced
this issue
Sep 14, 2022
s1hofmann
added a commit
that referenced
this issue
Oct 12, 2022
s1hofmann
added a commit
that referenced
this issue
Oct 12, 2022
…gProvider for timestamps and log levels
s1hofmann
added a commit
that referenced
this issue
Oct 12, 2022
s1hofmann
added a commit
that referenced
this issue
Oct 12, 2022
s1hofmann
added a commit
that referenced
this issue
Oct 12, 2022
s1hofmann
added a commit
that referenced
this issue
Oct 26, 2022
s1hofmann
added a commit
that referenced
this issue
Dec 15, 2022
s1hofmann
added a commit
that referenced
this issue
Dec 15, 2022
s1hofmann
added a commit
that referenced
this issue
Dec 15, 2022
* (#371) Added first definition of log provider interface * (#371) First draft implementation of a log provider * (#371) Register log provider in registry * (#371) Export function to connect external logger * (#371) First test log * (#371) Restructured log providers * (#371) Restructured logging code, extended functionality of ConsoleLogProvider for timestamps and log levels * (#371) Removed dev code from mouse.class * (#371) Added log output to provider registry * (#371) Updated exports * (#371) Introduced dedicated folder for log providers * (#371) Started adding log output to window.function.ts, sleep.function.ts and screen.class.ts * (#371) More log output for screen.class.ts * (#371) Clipboard logging * (#371) Fixed tests * Deleted debug file * (#371) Updated .gitignore * (#371) Added early returns to image processor + test case * (#371) ConsoleLogProvider test
s1hofmann
added
DONE
Implementation is done, but not yet merged into master
and removed
WIP
Work in progress
labels
Dec 15, 2022
s1hofmann
added a commit
that referenced
this issue
Dec 15, 2022
… on screen.find, refine log output on providerregistry
s1hofmann
added a commit
that referenced
this issue
Jan 16, 2023
s1hofmann
added a commit
that referenced
this issue
Jan 16, 2023
s1hofmann
added a commit
that referenced
this issue
Jan 16, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Short overview
nut.js currently does not provide any log output about it's internal processes.
In some cases, this is unfortunate as it would give users a deeper understanding on why things are the way they are.
With the new provider API a new logging provider could be established that allows to hook up nut.js to an existing loggin framework to output logs into an existing log stream
The text was updated successfully, but these errors were encountered: