mirror/opensourcepos
1
0 Fork 0
mirror of https://github.com/opensourcepos/opensourcepos.git synced 2026-10-04 08:35:31 -04:00
Code Issues Packages Projects Releases Wiki Activity

Change tense on trigger name for consistency

Browse Source 
Signed-off-by: objec <objecttothis@gmail.com>
This commit is contained in:
objec committed 2026-05-29 15:15:50 +04:00
1 parent b18e9ea785
commit 0e10a85248
2 files changed
+4 -4
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

app/Controllers/Sales.php
+1 -1
View File
@@ -917,7 +917,7 @@ class Sales extends Secure_Controller
}
$data['receipt_template_view'] = $receipt_template;
Events::trigger('sale_complete', $data['sale_id_num'], $sale_type);
Events::trigger('sale_completed', $data['sale_id_num'], $sale_type);
$this->sale_lib->clear_all();
return view('sales/receipt', $data);
app/Plugins/README.md
+3 -3
View File
@@ -101,7 +101,7 @@ OSPOS fires these events that plugins can listen to:
| `customer_saved` | `array $customerIds` | Customer created/updated via form save or CSV import |
| `customer_deleted` | `int $personId, string $email` | Customer deleted |
| `item_saved` | `array $itemIds` | Item created/updated via form save or CSV import |
| `sale_complete` | `int $saleIdNum, string $saleType` | Sale finalized and receipt rendered |
| `sale_completed` | `int $saleIdNum, string $saleType` | Sale finalized and receipt rendered |
| `receiving_complete` | `int $receivingId, string $mode` | Receiving finalized and items added to inventory |
> **Note:** `customer_saved` and `item_saved` always receive an array of IDs.
@@ -254,7 +254,7 @@ class MyPlugin extends BasePlugin
public function registerEvents(): void
{
Events::on('sale_complete', [$this, 'onSaleComplete']);
Events::on('sale_completed', [$this, 'onSaleComplete']);
Events::on('item_saved', [$this, 'onItemSaved']);
Events::on('receiving_complete', [$this, 'onReceivingComplete']);
}
@@ -532,7 +532,7 @@ For custom tables, plugins can create them during `install()` and drop them duri
## Event Flow
1. Application triggers event: `Events::trigger('sale_complete', $saleIdNum, $saleType)`
1. Application triggers event: `Events::trigger('sale_completed', $saleIdNum, $saleType)`
2. PluginManager recursively scans `app/Plugins/` directory
3. Each enabled plugin registers its listeners via `registerEvents()`
4. Events::on() callbacks are invoked automatically