-
Notifications
You must be signed in to change notification settings - Fork 96
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
glog #26
Comments
It was reasonably conventional at the time. I’d be happy for it to be gone and replaced with a cas.Logger interface or something. I’m not longer in a position where I use CAS authentication so I’ve not really visited this code for a while though it does need cleaning and updating for more modern styles.
…Sent from my iPhone
On 7 Nov 2018, at 00:00, Johan Dahl ***@***.***> wrote:
Hi
Thanks for providing a really useful package
What is the idea behind using glog? It's repository hasn't been updated in 4 years and It is a little bit annoying to have a hardcoded logging package inside a library.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
I will start to work for this issue. |
Open
@bbiao: Any news on that? Whats the plan for logging? Maybe someone else can to implement help here if there is already a plan. |
Logging modification is almost done, currently I'm doing tests and code review by myself. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi
Thanks for providing a really useful package
What is the idea behind using glog? It's repository hasn't been updated in 4 years and It is a little bit annoying to have a hardcoded logging package inside a library.
The text was updated successfully, but these errors were encountered: