Skip to content

Correctly set field name for @TargetMethodOrField #700

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.

Sign up for GitHub

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

Jump to bottom
Merged
jbachorik merged 1 commit into from
Oct 13, 2024
Merged

Correctly set field name for @TargetMethodOrField #700

jbachorik merged 1 commit into from
Oct 13, 2024

Conversation

@yewton
Copy link
Contributor

@yewton yewton commented Oct 11, 2024

Fixes #694

jbachorik
jbachorik approved these changes Oct 12, 2024
View reviewed changes
Copy link
Collaborator

@jbachorik jbachorik left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looking good!

Thanks again for the contribution!

@jbachorik jbachorik added this pull request to the merge queue Oct 13, 2024
Merged via the queue into btraceio:develop with commit fa81dce Oct 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@jbachorik jbachorik jbachorik approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

@TargetMethodOrFiled gives user provided specification value instead of instrumented object's value when used with Kind.FIELD_GET or Kind.FIELD_SET

2 participants

@yewton @jbachorik