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
I tried dropping an email previously but didn't receive a response. I'm curious on your stance of the meta-logging currently used in the loggerui. In particular the 'adding logrecord' and 'logrecord added'.
At the moment the way it is configured it results in a 2nd event being fired during an event which throws an exception. Uncaught Error: Bad state: Cannot fire new event. Controller is already firing an event
Now as is, I can see two methods of fixing the error. The first is to manually adding the meta-logging to the List, however this will mean that the (console) print functionality work if that's enabled.
The second method is to add the meta logging with a Timer to put it at the end of the event loop. This however will mean that the meta-logging is out of order and loses context.
My personally preference however would be to remove the meta-logging entirely from the library and allow it to be added by the users at their discretion.
Before I submit a pull request for the Polymer fix I wanted to run this situation by you as well. Thanks.
The text was updated successfully, but these errors were encountered:
Hi Chris,
I tried dropping an email previously but didn't receive a response. I'm curious on your stance of the meta-logging currently used in the loggerui. In particular the 'adding logrecord' and 'logrecord added'.
At the moment the way it is configured it results in a 2nd event being fired during an event which throws an exception.
Uncaught Error: Bad state: Cannot fire new event. Controller is already firing an event
Now as is, I can see two methods of fixing the error. The first is to manually adding the meta-logging to the List, however this will mean that the (console) print functionality work if that's enabled.
The second method is to add the meta logging with a Timer to put it at the end of the event loop. This however will mean that the meta-logging is out of order and loses context.
My personally preference however would be to remove the meta-logging entirely from the library and allow it to be added by the users at their discretion.
Before I submit a pull request for the Polymer fix I wanted to run this situation by you as well. Thanks.
The text was updated successfully, but these errors were encountered: