Conversation
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
| $resolver->setAllowedTypes('ignore_exceptions', 'string[]'); | ||
| $resolver->setAllowedTypes('ignore_transactions', 'string[]'); | ||
| $resolver->setAllowedTypes('trace_propagation_targets', ['null', 'string[]']); | ||
| $resolver->setAllowedTypes('strict_trace_continuation', 'bool'); |
There was a problem hiding this comment.
Dead strict_trace_propagation option silently ignored after rename
Medium Severity
The strict_trace_propagation option is still registered with setAllowedTypes and given a default value, but its getter (isStrictTracePropagationEnabled) and setter (enableStrictTracePropagation) were renamed to isStrictTraceContinuationEnabled / enableStrictTraceContinuation which now read from strict_trace_continuation. Any user passing 'strict_trace_propagation' => true in their options will have the setting silently accepted but completely ignored — the strict trace checking won't activate.
Additional Locations (1)
1 participant
Merges the current
masterinto5.x