-
Notifications
You must be signed in to change notification settings - Fork 0
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
Remaining API endpoints #65
Comments
Perhaps @ribose-jeffreylau can clarify? |
App Data:None of the actions ( App RelationNothing else is needed. CalendarYes, Events
|
@PeterTKY will be able to provide API information on Calendar and Events. |
Thanks, @ribose-jeffreylau! What about the following ones? WidgetWe only have StreamWe only have Space FileWe have SpaceWe have SettingsWe have MessagesWe have MembersWe only have LeaderboardWe only have FeedWe only have ConversationWe have |
@abunashir we need full implementation for:
In general the endpoints should support |
Thanks, @ronaldtse! We already have the support for |
@abunashir in this case should we always provide a default |
@ronaldtse: In some cases, yes, like we are doing here: https://github.com/riboseinc/ribose-ruby/blob/master/lib/ribose/connection.rb#L15 but if the resource provides the complete results then we did not pass anything as default. |
Great, Thanks, @ribose-jeffreylau. I will start implementing those soon :) |
@abunashir We can skip implementation of |
Thanks, @ribose-jeffreylau! Btw, Did you have a chance to check the events API? |
App Data:
Do we need to any other action like
fetch
,create
,edit
,update
ordestroy
here?Source: https://github.com/riboseinc/ribose-ruby/blob/master/lib/ribose/app_data.rb
App Relation
Is there anything else on this API endpoint?
Source: https://github.com/riboseinc/ribose-ruby/blob/master/lib/ribose/app_relation.rb
Calendar
Do you need any
remove
ordelete
action for this one?Source: https://github.com/riboseinc/ribose-ruby/blob/master/lib/ribose/calendar.rb
Events
We haven't implement anything on that one yet!
The text was updated successfully, but these errors were encountered: