-
Notifications
You must be signed in to change notification settings - Fork 1
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
Add discussion service and associated types #111
Conversation
cb21798
to
fc1b0cf
Compare
Co-authored-by: Charlotte Emms <[email protected]> Co-authored-by: George B <[email protected]> Co-authored-by: Jamie B <[email protected]>
fc1b0cf
to
bb0d332
Compare
|
struct DiscussionApiResponse { | ||
1: required string status; | ||
2: required i32 statusCode; | ||
3: required string message; | ||
4: optional string errorCode; | ||
} |
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.
Not sure if errorCode
can be absent if status is 'error'
or present if status is 'ok'
. Maybe a union type similar to what we do in DCR would be more appropriate?
The previous stub was unused. This adds relevant types and signatures for the `recommend` method. This PR is based off commits in #111. This change adds `recommend` by itself so that it can be implemented soon by Android and iOS. We can release the remaining Discussion methods in another Bridget version, so the platforms can implement them when ready. This will enable us to render more articles with discussion using DCAR, more quickly. Co-authored-by: Jamie B <[email protected]> Co-authored-by: Ioanna Kokkini <[email protected]> Co-authored-by: Charlotte <[email protected]>
* Replace Discussion stubs with new recommend signature + types The previous stub was unused. This adds relevant types and signatures for the `recommend` method. This PR is based off commits in #111. This change adds `recommend` by itself so that it can be implemented soon by Android and iOS. We can release the remaining Discussion methods in another Bridget version, so the platforms can implement them when ready. This will enable us to render more articles with discussion using DCAR, more quickly. Co-authored-by: Jamie B <[email protected]> Co-authored-by: Ioanna Kokkini <[email protected]> Co-authored-by: Charlotte <[email protected]>
Superceded by #154 |
What does this change?
Adds thrift definitions for the
Discussion
service needed to allow the web view to communicate with the discussion API via native layer of the apps. These tend to be authenticated methods as the unauthenticated ones can be done via the web view alone.