-
Notifications
You must be signed in to change notification settings - Fork 28
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
EventType names do not match actual events messages names #79
Comments
Hello @n0izn0iz . You have a valid point. I agree that we should make breaking API changes now. I have a question. In general the API call is a "verb" and the resulting event is a "noun". For example the API call |
This seems ok, it's not the api call that don't match, it's the event types and messages, in this case, both will be "Added" I think in the case of |
Signed-off-by: Jeff Thompson <jeff@thefirst.org>
…ent. Fixes berty#79. Signed-off-by: Jeff Thompson <jeff@thefirst.org>
…ent. Fixes berty#79. Signed-off-by: Jeff Thompson <jeff@thefirst.org>
🎉 This issue has been resolved in version 1.12.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Is there an existing issue for this?
Package version
v1.10.0
OS
Other
Language version and compiler version
go1.20.4
Bug description
Some event messages names do not match their EventType name
For example the message corresponding to
EventType.AccountContactRequestIncomingReceived
is actually calledAccountContactRequestReceived
This is annoying for writing generic events decoders (it's useful for dumping payloads for example)
I wrote a little script to find inconsistent event naming
Current behavior
Some event messages names do not match their EventType name
Expected behavior
All events messages names do match their EventType name
Environment
macOS 13.3.1
Other
Since this is an api breaking change I would recommend fixing this before the api is widely consumed
The text was updated successfully, but these errors were encountered: