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

Support sending events without an event: field for the event name #15

Merged
merged 1 commit into from
Dec 5, 2020

Conversation

joshtriplett
Copy link
Member

The event field is optional in the specification, and adds overhead,
which some applications do not want. Allow omitting it.

To simplify use, accept the name as impl Into<Option<&str>>, which
allows existing code that passes "name" to continue working. Since
this can potentially cause an inference failure in code that previously
compiled, bump the major version, but most code should continue
working with just a recompile.

The event field is optional in the specification, and adds overhead,
which some applications do not want. Allow omitting it.

To simplify use, accept the name as `impl Into<Option<&str>>`, which
allows existing code that passes `"name"` to continue working. Since
this can potentially cause an inference failure in code that previously
compiled, bump the major version, but *most* code should continue
working with just a recompile.
@jbr jbr merged commit f52512c into http-rs:main Dec 5, 2020
@jbr
Copy link
Member

jbr commented Dec 5, 2020

👍

@joshtriplett joshtriplett deleted the unnamed-events branch September 19, 2021 04:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants