chore: drop L5, support L6 and L7

README.md

@@ -1,8 +1,8 @@
-#  OneSignal REST API Wrapper For Laravel/Lumen
+# OneSignal REST API Wrapper For Laravel/Lumen
 
 ## Introduction
 
-This project is a Laravel 5 / Lumen wrapper for the OneSignal REST API v1.
+This project is a Laravel 6+ / Lumen wrapper for the OneSignal REST API v1.
 It supports all operations currently supported by the API.
 
 ## Installation (Laravel and Lumen)
@@ -14,37 +14,26 @@ composer require dreamonkey/laravel-onesignal-rest-api
 ```
 
 ## Laravel Users:
-From Laravel 5.5 onwards, it's possible to take advantage of auto-discovery of the service provider.
 
-For Laravel versions before 5.5, you must register the service provider in your config/app.php
-
-Update `config/app.php` by adding the following entries.
-```php
-'providers' => [
-    // ...
-    Dreamonkey\OneSignal\OneSignalServiceProvider::class,
-];
-
-'aliases' => [
-   	// ...
-   	'OneSignal' => Dreamonkey\OneSignal\Facades\OneSignal::class,
-];
-```
+Service provider will be auto-discovered.
 
 ## Lumen Users:
+
 Update `bootstrap/app.php`, adding the following entry
+
 ```php
 $app->register( \Dreamonkey\OneSignal\OneSignalServiceProvider::class );
 class_alias( 'Dreamonkey\OneSignal\OneSignalFacade', 'OneSignal' );
 ```
 
-
 ## Configuration
+
 There are three values that need to be set in order to use the library: your default OneSignal app ID, the REST API key and your account User Auth Key.
 All of these items can be found in your Control Panel on the OneSignal site.
 First two are app-related and can be found inside your app settings in the "Keys & IDs" tab (upper left corner), the third is account-related and can be found pressing your account avatar (lower right corner) and selecting "Account & API Keys".
 
 Place the 3 keys into your .env file, as such:
+
 ```
 ONESIGNAL_APP_ID=
 ONESIGNAL_REST_API_KEY=
@@ -53,8 +42,9 @@ ONESIGNAL_USER_AUTH_KEY=
 
 ## Usage
 
-There is a function for each of the OneSignal API calls.  They are broken down here.
+There is a function for each of the OneSignal API calls. They are broken down here.
 All methods will return an array formatted like this:
+
 ```
     [
         'status' => < HTTP status code of the request >,
@@ -64,46 +54,48 @@ All methods will return an array formatted like this:
     ]
 ```
 
-**Note:** In all instances where an $app_id is asked for, omitting it will grab the default OneSignal App ID specified in the .env file
+**Note:** In all instances where an \$app_id is asked for, omitting it will grab the default OneSignal App ID specified in the .env file
 
 ### Apps
 
 ##### getApps() - Get all Apps for the user
+
 ```
 $response = OneSignal::getApps();
 ```
 
-##### getApp( $app_id ) - Get the given App
+##### getApp( \$app_id ) - Get the given App
 
-##### postapp( $data ) - Create a new App
+##### postapp( \$data ) - Create a new App
 
 ##### putApp( $app_id, $data ) - Update an App
 
 ### Players
 
-##### getPlayers( $app_id, $limit, $offset ) - Get Players from an App
+##### getPlayers( $app_id, $limit, \$offset ) - Get Players from an App
 
-##### getPlayer( $id ) - Get Player of the given ID
+##### getPlayer( \$id ) - Get Player of the given ID
 
 ##### postPlayer ( $data, $app_id ) - Add Player to an App
 
 ##### putPlayer( $data, $app_id ) - Update Player object for an App
 
-##### postCSVExport( $app_id ) - Get a CSV dump of all Players for an App
+##### postCSVExport( \$app_id ) - Get a CSV dump of all Players for an App
 
-##### postPlayerOnSession( $data ) - Start a new device session for this Player
+##### postPlayerOnSession( \$data ) - Start a new device session for this Player
 
-##### postPlayerOnPurchase( $data ) - Track a new purchase for this Player
+##### postPlayerOnPurchase( \$data ) - Track a new purchase for this Player
 
-##### postPlayerOnFocus( $data ) - Increment the Players total session length
+##### postPlayerOnFocus( \$data ) - Increment the Players total session length
 
 ### Notifications
 
-##### getNotifications( $app_id, $limit, $offset ) - Get all Notifications for an App
+##### getNotifications( $app_id, $limit, \$offset ) - Get all Notifications for an App
 
 ##### getNotification( $id,  $app_id ) - Get a Notification from an App
 
 ##### postNotification( $data, $app_id ) - Add a Notification to an App
+
 ```
 $response = OneSignal::postNotification([
     "tags"                  =>  [ ["key" => "myKey", "relation" => "=", "value" => 1 ] ],
@@ -112,16 +104,15 @@ $response = OneSignal::postNotification([
 ]);
 ```
 
-##### putNotificationTrackOpen( $id, $app_id, $opened ) - Track whether a Notification was opened
+##### putNotificationTrackOpen( $id, $app_id, \$opened ) - Track whether a Notification was opened
 
 ##### deleteNotification( $id, $app_id ) - Delete a Notification from an App
 
-
-
 ## References
+
 The official OneSignal API documentation is listed here:
 https://documentation.onesignal.com/docs/server-api-overview
 
-
 ## Acknowledgements
+
 This project has been forked and evolved by Dreamonkey from https://github.com/jmrieger/onesignal-laravel

composer.json

@@ -1,12 +1,19 @@
 {
   "name": "dreamonkey/laravel-onesignal-rest-api",
   "description": "OneSignal REST API Wrapper For Laravel/Lumen",
-  "keywords": ["onesignal", "webpush", "push", "laravel", "laravel 5", "lumen", "rest"],
+  "keywords": [
+    "onesignal",
+    "webpush",
+    "push",
+    "laravel",
+    "lumen",
+    "rest"
+  ],
   "type": "library",
   "require": {
-    "php": ">=5.5",
+    "php": ">=7.2",
     "guzzlehttp/guzzle": "^6.2",
-    "illuminate/support": "4.*|5.*",
+    "illuminate/support": "6.*|7.*",
     "symfony/psr-http-message-bridge": "^1.0.0"
   },
   "require-dev": {