onramplab/elevenlabs-api-client

ElevenLabs API client

v1.0.1 2023-09-27 09:39 UTC

Requires

• php: >=7.4
• onramplab/php-api-client: ^2.0

Requires (Dev)

• mockery/mockery: ^1.5
• nunomaduro/phpinsights: ^2.6
• onramplab/onr-phpcs-laravel: ^1.2
• phpmd/phpmd: ^2.13
• phpstan/phpstan: ^1.9
• phpunit/phpunit: ^9.5
• rector/rector: ^0.15.3
• sempro/phpunit-pretty-print: ^1.4
• spatie/phpunit-watcher: ^1.23
• squizlabs/php_codesniffer: *

MIT

• Onramplab

• package
• composer
• text-to-speech
• elevenlabs

README

Requirements

• PHP >= 7.4;
• composer.

Features

• PSR-4 autoloading compliant structure;
• PSR-2 compliant code style;
• Unit-Testing with PHPUnit 6;
• Comprehensive guide and tutorial;
• Easy to use with any framework or even a plain php file;
• Useful tools for better code included.

Installation

composer require onramplab/elevenlabs-api-client

This will create a basic project structure for you:

• /build is used to store code coverage output by default;
• /src is where your codes will live in, each class will need to reside in its own file inside this folder;
• /tests each class that you write in src folder needs to be tested before it was even "included" into somewhere else. So basically we have tests classes there to test other classes;
• .gitignore there are certain files that we don't want to publish in Git, so we just add them to this fle for them to "get ignored by git";
• CHANGELOG.md to keep track of package updates;
• CONTRIBUTION.md Contributor Covenant Code of Conduct;
• LICENSE terms of how much freedom other programmers is allowed to use this library;
• README.md it is a mini documentation of the library, this is usually the "home page" of your repo if you published it on GitHub and Packagist;
• composer.json is where the information about your library is stored, like package name, author and dependencies;
• phpunit.xml It is a configuration file of PHPUnit, so that tests classes will be able to test the classes you've written;
• .travis.yml basic configuration for Travis CI with configured test coverage reporting for code climate.

Please refer to original article for more information.

Useful Tools

Running Tests:

php vendor/bin/phpunit

or

composer test

Code Sniffer Tool:

php vendor/bin/phpcs --standard=PSR2 src/

or

composer psr2check

Code Auto-fixer:

composer psr2autofix
composer insights:fix
composer rector:fix

Building Docs:

php vendor/bin/phpdoc -d "src" -t "docs"

or

composer docs

Changelog

To keep track, please refer to CHANGELOG.md.

Contributing

1. Fork it.
2. Create your feature branch (git checkout -b my-new-feature).
3. Make your changes.
4. Run the tests, adding new ones for your own code if necessary (phpunit).
5. Commit your changes (git commit -am 'Added some feature').
6. Push to the branch (git push origin my-new-feature).
7. Create new pull request.

Also please refer to CONTRIBUTION.md.

License

Please refer to LICENSE.