Skip to content
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

IntrospectionProcessor returns also information about call type #1612

Merged
merged 1 commit into from Mar 18, 2022
Merged

IntrospectionProcessor returns also information about call type #1612

merged 1 commit into from Mar 18, 2022

Conversation

jszczypk
Copy link
Contributor

$record['extra']['callType'] will contain current call type: "->" or "::" depending if it was normal or static method call.
Gives possibility to nicely format messages "{$record['extra']['class']}{$record['extra']['callType']}{$record['extra']['function']} ..."

$record['extra']['callType'] will contain current call type: "->" or "::" depending if it was normal or static method call.
Gives possibility to nicely format messages "{$record['extra']['class']}{$record['extra']['callType']}{$record['extra']['function']} ..."
@jszczypk jszczypk changed the title added information about call type from debug_backtrace IntrospectionProcessor returns also information about call type Nov 24, 2021
@Seldaek Seldaek added this to the 3.x milestone Mar 6, 2022
@Seldaek
Copy link
Owner

Seldaek commented Mar 6, 2022

Scheduling for 3.0 because adding this here seems like it could potentially break stuff.. Some log backends like Elasticsearch kinda depend on the shape of logs and if things change like this it may cause issues, so if it's only about nicer formatting but doesn't bring any other value it doesn't seem really worth the risk in a minor release.

@jszczypk
Copy link
Contributor Author

@Seldaek It is impossible for this patch to break anything - it's just additional field in extra, so Elasticsearch and others will continue to work as they work now.
Other projects will have the possibility to start using this feature from new minor version.
You can safely move it to 2.5.0

@Seldaek Seldaek modified the milestones: 3.x, 2.x Mar 18, 2022
@Seldaek
Copy link
Owner

Seldaek commented Mar 18, 2022

Ah right I guess the problem was with keys of variable types, not new keys

@Seldaek Seldaek merged commit f0e0dba into Seldaek:main Mar 18, 2022
@lyrixx lyrixx mentioned this pull request Aug 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants