Fix readme

Author: asvae

README.md

@@ -1,194 +1,15 @@
-## Laravel Debugbar
-[![Packagist License](https://poser.pugx.org/barryvdh/laravel-debugbar/license.png)](http://choosealicense.com/licenses/mit/)
-[![Latest Stable Version](https://poser.pugx.org/barryvdh/laravel-debugbar/version.png)](https://packagist.org/packages/barryvdh/laravel-debugbar)
-[![Total Downloads](https://poser.pugx.org/barryvdh/laravel-debugbar/d/total.png)](https://packagist.org/packages/barryvdh/laravel-debugbar)
-
-### For Laravel 4, please use the [1.8 branch](https://github.com/barryvdh/laravel-debugbar/tree/1.8)!
-
-This is a package to integrate [PHP Debug Bar](http://phpdebugbar.com/) with Laravel 5.
-It includes a ServiceProvider to register the debugbar and attach it to the output. You can publish assets and configure it through Laravel.
-It bootstraps some Collectors to work with Laravel and implements a couple custom DataCollectors, specific for Laravel.
-It is configured to display Redirects and (jQuery) Ajax Requests. (Shown in a dropdown)
-Read [the documentation](http://phpdebugbar.com/docs/) for more configuration options.
-
-![Screenshot](https://cloud.githubusercontent.com/assets/973269/4270452/740c8c8c-3ccb-11e4-8d9a-5a9e64f19351.png)
-
-Note: Use the DebugBar only in development. It can slow the application down (because it has to gather data). So when experiencing slowness, try disabling some of the collectors.
-
-This package includes some custom collectors:
- - QueryCollector: Show all queries, including binding + timing
- - RouteCollector: Show information about the current Route.
- - ViewCollector: Show the currently loaded views. (Optionally: display the shared data)
- - EventsCollector: Show all events
- - LaravelCollector: Show the Laravel version and Environment. (disabled by default)
- - SymfonyRequestCollector: replaces the RequestCollector with more information about the request/response
- - LogsCollector: Show the latest log entries from the storage logs. (disabled by default)
- - FilesCollector: Show the files that are included/required by PHP. (disabled by default)
- - ConfigCollector: Display the values from the config files. (disabled by default)
-
-Bootstraps the following collectors for Laravel:
- - LogCollector: Show all Log messages
- - SwiftMailCollector and SwiftLogCollector for Mail
-
-And the default collectors:
- - PhpInfoCollector
- - MessagesCollector
- - TimeDataCollector (With Booting and Application timing)
- - MemoryCollector
- - ExceptionsCollector
-
-It also provides a Facade interface for easy logging Messages, Exceptions and Time
+# Laravel Api Tester
 
 ## Installation
 
 Require this package with composer:
 
 ```
-composer require barryvdh/laravel-debugbar
+composer require asvae/laravel-api-tester
 ```
 
 After updating composer, add the ServiceProvider to the providers array in config/app.php
-> If you use a catch-all/fallback route, make sure you load the Debugbar ServiceProvider before your own App ServiceProviders.
-
-### Laravel 5.x:
-
-```
-Asvae\ApiTester\\ServiceProvider::class,
-```
-
-If you want to use the facade to log messages, add this to your facades in app.php:
-
-```
-'Debugbar' => Barryvdh\Debugbar\Facade::class,
-```
-
-
-The profiler is enabled by default, if you have app.debug=true. You can override that in the config (`debugbar.enabled`). See more options in `config/debugbar.php`
-You can also set in your config if you want to include/exclude the vendor files also (FontAwesome, Highlight.js and jQuery). If you already use them in your site, set it to false.
-You can also only display the js of css vendors, by setting it to 'js' or 'css'. (Highlight.js requires both css + js, so set to `true` for syntax highlighting)
-
-Copy the package config to your local config with the publish command:
-
-```
-php artisan vendor:publish
-```
-
-### Lumen:
-
-For Lumen, register a different Provider in `bootstrap/app.php`:
-
-```
-if (env('APP_DEBUG')) {
- $app->register(Barryvdh\Debugbar\LumenServiceProvider::class);
-}
-```
-
-To change the configuration, copy the file to your config folder and enable it:
-
-```
-$app->configure('debugbar');
-```
-
-## Usage
-
-You can now add messages using the Facade (when added), using the PSR-3 levels (debug, info, notice, warning, error, critical, alert, emergency):
-
-```php
-Debugbar::info($object);
-Debugbar::error('Error!');
-Debugbar::warning('Watch out…');
-Debugbar::addMessage('Another message', 'mylabel');
-```
-
-And start/stop timing:
-
-```php
-Debugbar::startMeasure('render','Time for rendering');
-Debugbar::stopMeasure('render');
-Debugbar::addMeasure('now', LARAVEL_START, microtime(true));
-Debugbar::measure('My long operation', function() {
-    // Do something…
-});
-```
-
-Or log exceptions:
-
-```php
-try {
-    throw new Exception('foobar');
-} catch (Exception $e) {
-    Debugbar::addException($e);
-}
-```
-
-There are also helper functions available for the most common calls:
-
-```php
-// All arguments will be dumped as a debug message
-debug($var1, $someString, $intValue, $object);
-
-start_measure('render','Time for rendering');
-stop_measure('render');
-add_measure('now', LARAVEL_START, microtime(true));
-measure('My long operation', function() {
-    // Do something…
-});
-```
-
-If you want you can add your own DataCollectors, through the Container or the Facade:
-
-```php
-Debugbar::addCollector(new DebugBar\DataCollector\MessagesCollector('my_messages'));
-//Or via the App container:
-$debugbar = App::make('debugbar');
-$debugbar->addCollector(new DebugBar\DataCollector\MessagesCollector('my_messages'));
-```
-
-By default, the Debugbar is injected just before `</body>`. If you want to inject the Debugbar yourself,
-set the config option 'inject' to false and use the renderer yourself and follow http://phpdebugbar.com/docs/rendering.html
-
-```php
-$renderer = Debugbar::getJavascriptRenderer();
-```
-
-Note: Not using the auto-inject, will disable the Request information, because that is added After the response.
-You can add the default_request datacollector in the config as alternative.
-
-## Enabling/Disabling on run time
-You can enable or disable the debugbar during run time.
-
-```php
-\Debugbar::enable();
-\Debugbar::disable();
-```
-
-NB. Once enabled, the collectors are added (and could produce extra overhead), so if you want to use the debugbar in production, disable in the config and only enable when needed.
-
-
-## Twig Integration
-
-Laravel Debugbar comes with two Twig Extensions. These are tested with [rcrowe/TwigBridge](https://github.com/rcrowe/TwigBridge) 0.6.x
-
-Add the following extensions to your TwigBridge config/extensions.php (or register the extensions manually)
-
-```php
-'Barryvdh\Debugbar\Twig\Extension\Debug',
-'Barryvdh\Debugbar\Twig\Extension\Dump',
-'Barryvdh\Debugbar\Twig\Extension\Stopwatch',
-```
-
-The Dump extension will replace the [dump function](http://twig.sensiolabs.org/doc/functions/dump.html) to output variables using the DataFormatter. The Debug extension adds a `debug()` function which passes variables to the Message Collector,
-instead of showing it directly in the template. It dumps the arguments, or when empty; all context variables.
-
-```
-{{ debug() }}
-{{ debug(user, categories) }}
-```
-
-The Stopwatch extension adds a [stopwatch tag](http://symfony.com/blog/new-in-symfony-2-4-a-stopwatch-tag-for-twig)  similar to the one in Symfony/Silex Twigbridge.
 
 ```
-{% stopwatch "foo" %}
-    …some things that gets timed
-{% endstopwatch %}
+Asvae\ApiTester\ServiceProvider::class,
 ```