-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Bug: Chrome logger does not work. #2616
Comments
Appreciate that you offered to look into it. I don’t use Chrome so I’m pretty unfamiliar with the structure but... any ideas why the tests are passing even if this has been broken for a while? |
I knew at one point, but have forgotten now. |
I refreshed my memory about the issue because I know y'all are curious why it passes the unit test but fails in the real world. The unit test method calls However. here is how
Except there isn't an event named 'post_controller', and a non-existent event won't be triggered. Obviously. |
You are so right! Good catch. I’d say just try switching to |
I tried the I actually have... er, that is, had a solution. I've made a mess of my local repo and cannot find the final working commit. It's in there somewhere. It would be nice to find since I tackled the @todo and worked out some fancy object formatting which users should appreciate. I also added logic so that the ChromeLogger cannot be instantiated in the production environment. We would be quite negligent to allow that to happen. I'm on it though. |
Fabulous. ;) I trust it to you |
Describe the bug
Plain and simple, doesn't work. I think the framework changed significantly since the code was first written. The event that was to send the headers doesn't exist any longer.
I discovered this some time ago and devised a fix but never made a PR on it.
Feel free to assign this one to me. It might take a little while to get time for it. I mostly need to devise some unit tests.
The text was updated successfully, but these errors were encountered: