Skip to content
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

Move logging to it's own file #172

Open
PallasDoesCode opened this issue Jul 17, 2016 · 0 comments
Open

Move logging to it's own file #172

PallasDoesCode opened this issue Jul 17, 2016 · 0 comments
Milestone

Comments

@PallasDoesCode
Copy link
Collaborator

While debugging the code I notice that there is only one method that handles all the logging for the project. However it does not differentiate between success and error messages. Because of this we are having to manually assign a color at the time we call the logging function. In order to make things easier I'm planning to move the logging function to it's own file. This will allow us to expand the logging so we can have more methods (for example: logging information vs errors), Informational logging will colored green and error logging will be colored red. There are more things that we can do to help improve logging I'll post them here when I decide what else we might want to add.

@PallasDoesCode PallasDoesCode added this to the 1.0.0 milestone Jul 17, 2016
@PallasDoesCode PallasDoesCode self-assigned this Jul 17, 2016
@PallasDoesCode PallasDoesCode removed their assignment Oct 16, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant