List view

• OAuth 1.a, OAuth 2 Bearer And making OAuthes work and being clear.

  To be honest, OAuth process of Twitter is a little complex for myself, and I think my implementation is not the best approach. Also using a third party and low maintained package doesn't make sense and we will change it soon. I want this package to do anything possible with Twitter, and OAuth is one of the defects that we should solve.

  No due date
  0% complete0 open0 closed

• API version 1.1

  Adding API version 1.1 is not a hard thing specially after doing other milestones, but anyway have its own challenges, First of all twitter doesn't give anyone access to this endpoint anymore, you need to have elevated access or more. I don't have anything more about this milestone for now, but I'll add additional information.

  No due date
  0% complete0 open0 closed

• Params parser

  We should take params in our methods, for example GetUserTweets get a param of max_results that has a default of 10 but can be set to get up to 100 tweets. or since_id which defines a date to get tweet from then on. there are so many other params that are not necessary, but can significantly change the final result. By now, we have params map[string]interface{} The important thing is the functionality and facility.

  No due date
  0% complete0 open0 closed

• Parse response and return twigo.Response instead of http.Response from client methods.

  By now, style of methods is like this: func (c *Client) FnName() (*http.Response, error) That we return *http.Response and then use Response.Body.read() or .close() and some more complexity, we should simplify the response for developers using this package. Also user has access to lots of other properties in the header which is not needed, is not a bad thing, but can be cleaner. So we should define a Response struct and return it, also its fields will include User struct or Tweet struct or Space struct and more...

  No due date
  0% complete0 open0 closed