You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
###Overview
Currently there are no logs being generated from running Octo. This can be quite confusing for everyone who wants to understand why something didn't run, or even to understand what is happening in the system.
Technical Considerations
In some places, console.error() is being used.
Most errors being thrown are very generic, without any identifying information.
There are no DEBUG/INFO logs.
Should customers/users be able to control the amount of logs being generated, by choosing the level of logging?
Tests such as action.decorator.spec.ts can use the logs to assert on testing.
Acceptance Criteria
Logging library introduced, and appropriate logs are generated on every action Octo does.
Tests depending on this feature should be fixed by adding log assertions.
The text was updated successfully, but these errors were encountered:
###Overview
Currently there are no logs being generated from running Octo. This can be quite confusing for everyone who wants to understand why something didn't run, or even to understand what is happening in the system.
Technical Considerations
console.error()
is being used.action.decorator.spec.ts
can use the logs to assert on testing.Acceptance Criteria
The text was updated successfully, but these errors were encountered: