feat: enhance address retrieval logic to allow viewing of other accou…

feat: enhance address retrieval logic to allow viewing of other accou…

feat: add method to set a single invoice address for the current account @ikhalilatteib

feat: add method to set a single invoice address for the current account
@ikhalilatteib

Fix the Commons category filter to exact-match

Fix the Commons category filter to exact-match
Finished job is updated
feat: add CheckAccountOnboarding middleware to enforce account setup …

Added object_type and object_id to common_categories table

Rafact: Added object_type and object_id to common_categories table
add relationships for tickets, kbArticles, and agentExpertises in Cat…

v1.18.5: Merge pull request #225 from nextdeveloper-nl/dev

Adds NextDeveloper\Commons\Helpers\ObjectHelper with three methods:

• getPublicObjectName() — strips \Database\Models from a full model class name (e.g. NextDeveloper\IAAS\Database\Models\VirtualMachines → NextDeveloper\IAAS\VirtualMachines)
• getPrivateObjectName() — reverses the above (short form → full model class)
• getObject() — resolves and fetches a model by object type and ID/UUID

Abstract action negative runtime bug fixed

fix: cast diffInMilliseconds to int to prevent float value in integer…
fix: use abs() on diffInMilliseconds to prevent negative runtime values

Pusher is_test feature added

N8NPusher: Added is_test metadata flag — when true, replaces /webhook/ with /webhook-test/ in the URL for n8n test trigger mode
PushersService: trigger() now creates a PusherLog (status=pending) and explicitly dispatches PushObjectJob on the pushers queue — decoupled from the created:PusherLogs event which was architecturally incorrect
PushObjectJob: Removed EVENTS constant; job is no longer event-driven, it is dispatched directly by trigger()

Decouple PushersService

Summary

PushersService::trigger() now creates the PusherLog (status=pending) and explicitly dispatches PushObjectJob — no longer relies on the created:NextDeveloper\Commons\PusherLogs event
Removed PushObjectJob::EVENTS constant — the job is no longer event-driven
Removed the status='processing' workaround and synchronous execute() call from trigger()

Why: Architecturally, a log creation event should not trigger its own delivery. The trigger point is PushersService::trigger(), not the DB write. The event-based binding was already commented out in BindEventsCommand.php with the note: "A Log cannot trigger an object. Object can create a log."
Test plan

Call PushersService::trigger($pusherId, $payload) and verify PushObjectJob is dispatched to the commons queue
Confirm the job executes the correct driver and the log transitions from pending → completed/failed
Verify no double-execution occurs

🤖 Generated with Claude Code

Pusher service trigger added

Pusher service trigger added

feat: Add GET /commons/timezones endpoint

docs: Update contact email to support@plusclouds.com
docs: Add library listing and community links to README
feat: Add GET /commons/timezones endpoint