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.

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

[crashtracker] consistent naming convention for operations #561

Open
danielsn opened this issue Jul 31, 2024 · 0 comments
Open

[crashtracker] consistent naming convention for operations #561

danielsn opened this issue Jul 31, 2024 · 0 comments

Comments

@danielsn
Copy link
Contributor 

          Minor: More as a naming comment, it's weird to me that profiling stuff is prefixed ("begin_profiling_op") but tracing stuff isn't ("insert_trace_id")?

(Perhaps begin_op would be the way to go?)

Originally posted by @ivoanjo in #551 (comment)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@danielsn