-
Notifications
You must be signed in to change notification settings - Fork 4
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
API does not match Release notes for 2.6 #140
Comments
I am looking at updating from a 2.5 to 3.0 version and trying to understand the changes, so just naturally I read the release notes from 2.5 to 2.6 to 3.0. It's not a problem for me; I need to read the actual docs which correctly show the snake_case signature functions. And do a manual "before" and "after" comparison. A revised table in the 3.0 release notes would have avoided any confusion. |
Noted, thank you for bringing it up. We are preparing API docs on our website and a migration guide from v2 to v3, to be published next week. I will also make sure to amend the release notes here as well to avoid any future confusion. |
I've updated the table in #105 We have also just published our docs for this latest version with an upgrade guide. |
Describe the bug
Release notes for 2.6 describe a new set of routines in CamelCase but the implementation is snake_case.
See #105 for code and PR text which conflicts.
See #126 for removal of now-deprecated methods from 2.6.x version in 3.0 version.
To Reproduce
Expected behavior
Expected different spelling according to description in #105.
Passage SDK Versions
Third-Party SDK Versions
The text was updated successfully, but these errors were encountered: