-
Notifications
You must be signed in to change notification settings - Fork 239
Clean API #73
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
Comments
Sweet! |
hey, I know you said it's WIP, but seems like last commit was 4 months ago :) |
1.0 mostly needs to be documented and some more beta testing in order to get released. Both @uzyn and myself are very busy at the moment so no active development currently. But it is intended to happen, although its hard to set any ETA for this all. Community contributions surely will help speed up things. |
Hey, |
@eridal Hi there, Would be great to some contibutions, there really isnt a roadmap, as most that was planned (inside my head) was changed/added already. Any further changes would be caused by alpha testing by others, running into issues and/or missing features. One big thing we are lacking is documentation and some guidelines for strategy authors to create or update strategies for Opauth 1.0 In order to help out at this stage, you would need to dive into the code and find out how it works. |
Hey this project is great!!
I think the project is trying to do too much, in the end all that we need is some good API for sending auth request, and then reading responses.. all the url, path, callback, is a mess, and I would like opauth to leave that to my own.
Is there a plan or roadmap for something like this?
The text was updated successfully, but these errors were encountered: