Download the PHP package benkle/deviantart without Composer
On this page you can find all versions of the php package benkle/deviantart. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package deviantart
An basic, thinly object-oriented wrapper for deviantARTs oAuth2 API
This library can be used to access []deviantARTs official oAuth2 API](https://www.deviantart.com/developers/), abstracting away authorization, request building and response parsing. Well, a little bit, anyway...
Requirements
- PHP 7.0+
- seinopsys/oauth2-deviantart 1.0+
Installation
The Library can be included in the usual way with composer:
Usage
First you need to create an instance of Seinopsys' oAuth provider for the library to use:
Next, you need to procure a stored token.
Now you can wrap the Api class around them.
And finally, Authorization!
In case you are in the handler called by initial authorization, you can hand the auth code as a second parameter to authorize:
Once you've done all that, you can use the API, e.g. like this:
The endpoints are grouped into sub-object in accordance with the
documentation and will return instances of \stdClass.
The only exception of this rule is the sta.sh submit, which returns the ApiRequest used so adding parts is easier:
FAQ
- Where are the curated endpoints? They are deprecated and you should not use them.
- Why do so many endpoints have an
$includeMatureparameter? They are in the Docs. I know that they seem senseless and probably won't work, but they also don't really hurt. - All but one endpoint return
\stdClass. Why? It's easier to type hint, and I don't need hydrators and entities. The library is after all basic and only thinly object-oriented. Maybe I'll write a more OOP library around this some day.
