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
fix(telescope): register RequestHandledListener and SetRequestLifecycleListener in ConfigProvider (#1043)
* Initial plan
* fix(telescope): auto-register RequestHandledListener and SetRequestLifecycleListener
The listeners were missing from ConfigProvider causing exceptions and non-200 status codes to not be captured after upgrading to v3.1.76. Users had to manually add these listeners which was error-prone.
Changes:
- Add RequestHandledListener and SetRequestLifecycleListener to ConfigProvider
- Update documentation to reflect automatic listener registration
- Add test to verify listeners are properly registered
Co-authored-by: huangdijia <[email protected]>
* fix(telescope): 移除类名中的反斜杠以简化代码
* 删除 ConfigProviderTest.php 测试文件
---------
Co-authored-by: copilot-swe-agent[bot] <[email protected]>
Co-authored-by: huangdijia <[email protected]>
To record gRPC requests, use the `grpc` middleware
41
+
To enable additional gRPC functionality, use the `grpc` middleware
70
42
71
43
```php
72
44
<?php
@@ -78,6 +50,8 @@ return [
78
50
];
79
51
```
80
52
53
+
> Note: Request tracking is automatically enabled via the RequestHandledListener. The TelescopeMiddleware is only needed for additional gRPC-specific functionality.
> TelescopeMiddleware or RequestHandledListener, you can choose one of them.
57
+
> Note: Request tracking is automatically enabled via the RequestHandledListener. The TelescopeMiddleware is only needed for additional gRPC-specific functionality.
0 commit comments