|
1 | 1 | # Custom SQS queue reader for Laravel
|
2 | 2 |
|
3 | 3 | [](https://packagist.org/packages/palpalani/laravel-sqs-queue-json-reader)
|
4 |
| -[](https://github.com/palpalani/laravel-sqs-queue-json-reader/actions?query=workflow%3ATests+branch%3Amaster) |
5 |
| -[](https://github.com/palpalani/laravel-sqs-queue-json-reader/actions?query=workflow%3A"Check+%26+fix+styling"+branch%3Amaster) |
| 4 | +[](https://github.com/palpalani/laravel-sqs-queue-json-reader/actions?query=workflow%3ATests+branch%3Amain) |
| 5 | +[](https://github.com/palpalani/laravel-sqs-queue-json-reader/actions?query=workflow%3A"Check+%26+fix+styling"+branch%3Amain) |
6 | 6 | [](https://packagist.org/packages/palpalani/laravel-sqs-queue-json-reader)
|
7 | 7 |
|
8 | 8 |
|
9 | 9 | Custom SQS queue reader for Laravel projects that supports raw JSON payloads.
|
10 | 10 | Laravel expects SQS messages to be generated in a
|
11 | 11 | specific format that includes job handler class and a serialized job.
|
12 | 12 |
|
13 |
| -Note: Implemented tm read multiple messages from queue. |
| 13 | +Note: Implemented to read multiple messages from queue. |
14 | 14 |
|
15 | 15 | But in certain cases you may want to parse messages from 3rd party
|
16 | 16 | applications, custom JSON messages and so on.
|
@@ -60,7 +60,7 @@ return [
|
60 | 60 | ];
|
61 | 61 | ```
|
62 | 62 |
|
63 |
| -If queue is not found in 'handlers' array, SQS payload is passed to default handler. |
| 63 | +If the queue is not found in 'handlers' array, SQS payload is passed to default handler. |
64 | 64 |
|
65 | 65 | Add `sqs-json` connection to your config/queue.php, Ex:
|
66 | 66 |
|
|
0 commit comments