Skip to content
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

show status implementation #662

Closed
wants to merge 29 commits into from

Conversation

DiogoAndre
Copy link
Contributor

My attempt to implement the show status api referenced in #574

thomaslee and others added 16 commits August 18, 2012 03:16
An incomplete implementation, but provides most of the important stuff
that would be needed to pull a home timeline from a third party client.

Seems to work well enough to be useful.

[hotsh#570]
Almost identical to GET /statuses/home_timeline.json (see hotsh#570), but
the user is explicitly specified by the caller.

Added a bit of error handling guff relating to users that can't be found
and/or when the caller provides us with questionable input.

[hotsh#562]
Similar to home_timeline and user_timeline

looks like it might be good to extract out preparing the json

this commit should satisfy  hotsh#572
Twiter-api GET /api/statuses/mention.json
simple start for hotsh#603 that will give a basic acceptance test that the api calls return
valid JSON
- acceptance testing for the api methods that have already been
  implemented.
- cleaned up require_relative backport to 1.8 line
user needs to be an instance variable

Signed-off-by: DiogoAndre <[email protected]>
@wilkie
Copy link
Contributor

wilkie commented Sep 28, 2012

You may want to remove that last commit and rebase with master as the travis issue was fixed there as well.

@DiogoAndre
Copy link
Contributor Author

Removed that last commit.

Shouldn't we instead merge master into twitter-api? I think it's is a better way of bringing the twitter-api branch up to speed with the latest changes in master, and not mess up recent commits to the branch.

makes sense?

@wilkie
Copy link
Contributor

wilkie commented Sep 28, 2012

if the goal is to merge this branch into master at a later date, you want to continue to rebase with master regularly.

thomaslee and others added 11 commits September 28, 2012 14:49
An incomplete implementation, but provides most of the important stuff
that would be needed to pull a home timeline from a third party client.

Seems to work well enough to be useful.

[hotsh#570]
Almost identical to GET /statuses/home_timeline.json (see hotsh#570), but
the user is explicitly specified by the caller.

Added a bit of error handling guff relating to users that can't be found
and/or when the caller provides us with questionable input.

[hotsh#562]
Similar to home_timeline and user_timeline

looks like it might be good to extract out preparing the json

this commit should satisfy  hotsh#572
simple start for hotsh#603 that will give a basic acceptance test that the api calls return
valid JSON
- acceptance testing for the api methods that have already been
  implemented.
- cleaned up require_relative backport to 1.8 line
user needs to be an instance variable

Signed-off-by: DiogoAndre <[email protected]>
@DiogoAndre
Copy link
Contributor Author

not sure if I did this rebase the right way...

@DiogoAndre
Copy link
Contributor Author

Closing this and adding changes in pull request #674.

@DiogoAndre DiogoAndre closed this Oct 5, 2012
@carols10cents
Copy link
Contributor

Blgh yeah I tried rebasing the twitter-api branch and pushing it and I had hoped that would magically make this pull req nicer, but it didn't help. Thank you for being willing to make a new one :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants