Formatting and support Laravel 10.x

Kidus363 · May 22, 2023 · f8be4b8 · f8be4b8
1 parent 8b5fd0e
commit f8be4b8
Show file tree

Hide file tree

Showing 6 changed files with 554 additions and 541 deletions.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -5,3 +5,7 @@ All notable changes to `chapa-laravel` will be documented in this file
 ## 1.0.0 - 201X-XX-XX
 
 - initial release
+
+## 1.0.1 - 2023-05-22
+
+- Supporting latest `Laravel version (10.x)`, formatting and other minor reported bugs.
diff --git a/README.md b/README.md
@@ -22,7 +22,6 @@ You can check [this](https://github.com/Chapa-Et/sdk-examples/tree/master/chapa-
 Open your .env file and add your public key, secret keys, and other environment variables like this:
 
 ```
-CHAPA_PUBLIC_KEY=FLWPUBK-xxxxxxxxxxxxxxxxxxxxx-X
 CHAPA_SECRET_KEY=FLWSECK-xxxxxxxxxxxxxxxxxxxxx-X
 CHAPA_WEBHOOK_SECRET='My_webook_secret_key123'
 ```
@@ -45,12 +44,14 @@ The current features have been implemented
 | Parameter                    | Type     | Required | Description                                                                                                                                                                                         |
 | :--------------------------- | :------- | :------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | `key`                        | `string` | **Yes**. | This will be your public key from Chapa. When on test mode use the test key, and when on live mode use the live key.                                                                                |
-| `email`                      | `string` | **Yes**. | A customer’s email. address.                                                                                                                                                                        |
+| `email`                      | `string` | **No**. | A customer’s email. address.                                                                                                                                                                        |
 | `amount`                     | `string` | **Yes**. | The amount you will be charging your customer.                                                                                                                                                      |
-| `first_name`                 | `string` | **Yes**. | A customer’s first name.                                                                                                                                                                            |
-| `last_name`                  | `string` | **Yes**. | A customer’s last name.                                                                                                                                                                             |
+| `first_name`                 | `string` | **No**. | A customer’s first name.                                                                                                                                                                            |
+| `last_name`                  | `string` | **No**. | A customer’s last name.                                                                                                                                                                             |
 | `tx_ref`                     | `string` | **Yes**. | A unique reference given to each transaction.                                                                                                                                                       |
-| `callback_url`               | `string` | **Yes**. | Function that runs when payment is successful. This should ideally be a script that uses the verify endpoint on the Paystack API to check the status of the transaction.                            |
+| `callback_url`               | `string` | **No**. | Function that runs when payment is successful. This should ideally be a script that uses the verify endpoint on the Chapa API to check the status of the transaction.    
+
+| `return_url`               | `string` | **No**. | A web address provided by the merchant to a payment gateway during payment integration. It serves as the destination where the payment gateway sends the customer after completing a payment transaction.                          |
 | `currency`                   | `string` | **Yes**. | The currency in which all the charges are made. Currency allowed is ETB.                                                                                                                            |
 | `customization[tiitle] `     | `string` | **No**.  | The customizations field (optional) allows you to customize the look and feel of the payment modal. You can set a logo, the store name to be displayed (title), and a description for the payment.. |
 | `customization[description]` | `string` | **No**.  | The customizations field (optional) allows you to customize the look and feel of the payment modal.                                                                                                 |

diff --git a/composer.json b/composer.json
@@ -13,12 +13,17 @@
             "name": "Kidus Yared",
             "email": "[email protected]",
             "role": "Developer"
+        }, 
+        {
+            "name": "Israel Goytom",
+            "email": "[email protected]",
+            "role": "CTO"
         }
     ],
     "require": {
-        "php": "^7.4|^8.0",
-        "guzzlehttp/guzzle": "^7.4.5",
-        "illuminate/support": "^5.0|^6.0|^7.0|^8.0|^9.0"
+        "php": "^7.4|^8.0|^8.1",
+        "guzzlehttp/guzzle": "^7.7.0",
+        "illuminate/support": "^5.0|^6.0|^7.0|^8.0|^9.0|^10.0"
     },
     "require-dev": {
         "orchestra/testbench": "^6.0",