Global Partition Resolver is ignored

[sebestenyb]

1. The BalancedDispatchable contains a base method of getPartitionKey()
2. The BalancedRedisQueue prioritise this method to resolve the partition in its resolvePartition method over the partitionResolver callback
3. Since every balanced job uses the BalancedDispatchable trait, every job implements the getPartitionKey, the global partition resolver is ignored.

I think the trait should not implement the getPartitionKey method, leaving it to the actual jobs, and the property checks should maybe be moved to the BalancedRedisQueue@resolvePartition(), before the method checks.

Fixes #6

[YanGusik]

Thanks for this PR! You've correctly identified the issue - the global partition_resolver is indeed ignored because getPartitionKey() always exists in the trait.

However, I think the order of checks in resolvePartition() should be adjusted. The current PR checks properties before the getPartitionKey() method, which could break existing code where users override getPartitionKey() in their jobs.

Proposed order:

protected function resolvePartition($job): string
{
    // 1. Explicitly set via onPartition()
    if (isset($job->partitionKey)) {
        return (string) $job->partitionKey;
    }

    // 2. Overridden in job class (now works correctly without trait method!)
    if (method_exists($job, 'getPartitionKey')) {
        return (string) $job->getPartitionKey();
    }

    // 3. Global resolver from config
    if (isset($this->partitionResolver)) {
        return (string) ($this->partitionResolver)($job);
    }

    // 4. Auto-detect from common properties
    foreach (['userId', 'user_id', 'tenantId', 'tenant_id'] as $prop) {
        if (property_exists($job, $prop) && $job->$prop !== null) {
            return (string) $job->$prop;
        }
    }

    return 'default';
}

This way:

• onPartition() has highest priority (explicit)
• Custom getPartitionKey() in job classes still works
• Global resolver finally works as a fallback
• Auto-detection from properties is the last resort

Could you update the PR with this order? Thanks!