-
Notifications
You must be signed in to change notification settings - Fork 243
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
Added conversations.list endpoint functionality and cursor request parameter functionality in base response class. #250
Conversation
…rameter functionality in base response class.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
FWIW, I grabbed these changes and they work as advertised with the new conversations endpoint as well as the issue that I attempted to fix in rejected PR #231
Expands the use of conversations to use an enum when specifying request instead of pure string. Expands on Inumedia#250
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi, once the indentation is fixed I can merge this. As a bit meta, this API seems odd, kinda curious why types
would be a comma delimited list rather than just a regular array?
The requested indentation issue was resolved. Are these changes good to go? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi, thanks for reminding me to look at this again.
I double checked the changes and noticed one of the new calls creates the Tuples for the parameters but never actually adds it to the list. Once that's done this can be approved and will just need to wait for me to merge + deploy the new nuget package
Resolves Issue #242
Resolves original bug identified in Pull Request #231