Skip to content
This repository has been archived by the owner on Dec 5, 2019. It is now read-only.

Improvement in Logging #12

Open
ksakash opened this issue May 21, 2018 · 5 comments
Open

Improvement in Logging #12

ksakash opened this issue May 21, 2018 · 5 comments
Labels
enhancement New feature or request

Comments

@ksakash
Copy link
Contributor

ksakash commented May 21, 2018

Currently error logging in the code is very poor and it becomes tremendously difficult to find a bug in logic of the code. So, we need to improve it so that we can figure out quickly where the fault is.

@Suryansh470
Copy link
Contributor

Can u elaborate exactly what is the problem ?

@ksakash
Copy link
Contributor Author

ksakash commented May 21, 2018

Problem is whenever we go to testing and if the code doesn't work in the way it was supposed to be, then it takes a lot of time to track down the error in logic and it ruins the whole testing. Better logging will help in better debugging.

@Mayankm96
Copy link
Member

It is a nice idea, how do you plan to store the log messages?

@Mayankm96 Mayankm96 added the enhancement New feature or request label May 21, 2018
@ksakash
Copy link
Contributor Author

ksakash commented May 21, 2018

I was just saying about information that is printed on the terminal. @Mayankm96 do you have any other thoughts??

@Suryansh470
Copy link
Contributor

Can we get it listed into a log file or write it into a separate file or console??

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants