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
We'd like to be able to log all errors in development mode so they are both displayed in the bar but also logged using (our instance of) ILogger.
This would help up us not only when debugging errors during AJAX calls or some server-server requests, there are multiple use cases where this is useful (we have a special page with links to all older bluescreens).
Currently, the are DevelopmentStrategy and ProductionStrategy classes but they are both internal and final. I understand it is for a reason but...
In 2.9.7, the internal method getStrategy has no return typehint so it is still possible to do some black magic like decorating the strategy to do both 😇 👿.
Since 2.10.0 the getStrategy has ProductionStrategy|DevelopmentStrategy return typehint so this ugly hack is not possible anymore.
Wouldn't it be possible to support such a feature or somehow make this ugly hack possible again 😇?
The text was updated successfully, but these errors were encountered:
We'd like to be able to log all errors in development mode so they are both displayed in the bar but also logged using (our instance of)
ILogger
.This would help up us not only when debugging errors during AJAX calls or some server-server requests, there are multiple use cases where this is useful (we have a special page with links to all older bluescreens).
Currently, the are
DevelopmentStrategy
andProductionStrategy
classes but they are both internal and final. I understand it is for a reason but...In
2.9.7
, the internal methodgetStrategy
has no return typehint so it is still possible to do some black magic like decorating the strategy to do both 😇 👿.Since
2.10.0
the getStrategy hasProductionStrategy|DevelopmentStrategy
return typehint so this ugly hack is not possible anymore.Wouldn't it be possible to support such a feature or somehow make this ugly hack possible again 😇?
The text was updated successfully, but these errors were encountered: