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

Version 2.0 goals #686

Open
abraham opened this Issue Jul 3, 2018 · 4 comments

Comments

Projects
None yet
2 participants
@abraham
Owner

abraham commented Jul 3, 2018

This s a summary of the plans for TwitterOAuth version 2.

Once released, 1.0 will only receive critical bug fixes. It will have it's own branch and master branch will be working towards the goals listed below. If you are interested in implementing any of these, go comment on the particular issue.

Planned

  • Drop support for PHP < 7.1 (#678)
  • Enable strict_types and type declarations (#679)
  • Switch to recorded HTTP requests in tests (#671)
  • Explore switching to guzzle (#680)
  • File class for handling media files (#681)
  • Response class for handling responses (#683)
  • Throw exceptions for non-2XX responses (#682)
  • Support additional API hosts (#684)
  • Add better per request configuration (#685)

Under consideration

  • Streaming support (#295)
  • Everything else in the issue tracker
@hlashish

This comment has been minimized.

hlashish commented Sep 16, 2018

@abraham I have used your latest twitter oAuth library for sending the direct message, I have attached the screenshot of my app permission and I am following the link "https://twitteroauth.com/" for documentation. Please help me out with this API **'https://twitteroauth.com/**'(POST), because it is always returning NULL. Please help me out with this.
app-permisions

@hlashish

This comment has been minimized.

hlashish commented Sep 16, 2018

Hi Sir
I am still waiting for your response, please help me out. I am stocked from almost a month , trying to figure out the cause.

@abraham

This comment has been minimized.

Owner

abraham commented Sep 16, 2018

@hlashish please create a new issue that describes exactly what you are trying to do, what you expect to happen and what is actually happening.

@hlashish

This comment has been minimized.

hlashish commented Sep 16, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment