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

Guard telemetry:execute/3 #105

Merged
merged 1 commit into from Feb 1, 2022
Merged

Guard telemetry:execute/3 #105

merged 1 commit into from Feb 1, 2022

Conversation

josevalim
Copy link
Contributor

No description provided.

Copy link

@GregMefford GregMefford left a comment

Choose a reason for hiding this comment

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

As discussed in Slack, this enforces that all telemetry that is executed can actually be attached-to, whereas before, it was possible to execute using an event name that could never be attached-to, since attach ensures it is a list.

The danger here would be that a library or application code would be doing this incorrectly and would now crash instead of just not doing anything. In that case, upgrading Telemetry to use this code would hopefully let them know quickly that there was a problem and they could roll back to the previous version of Telemetry until the incorrect code can be updated.

@josevalim
Copy link
Contributor Author

@GregMefford you are awesome for adding the context here, thanks.

@josevalim josevalim merged commit d3ba8b2 into main Feb 1, 2022
@josevalim
Copy link
Contributor Author

💚 💙 💜 💛 ❤️

@josevalim josevalim deleted the jv-guard branch February 1, 2022 16:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants