This is a follow up to the previous PR#57187 that extended SQS FIFO and fair queue support to mailables, notifications, and event listeners. This PR adds support for defining amessageGroup method on the job classes instead of requiring the use of theonGroup() method at time of dispatch. See discussion on previous PRstarting here.

Summary

Normal jobs, mailables, and notifications are actively dispatched by the user and have the ability to callonGroup() at the time of dispatch. However, event listeners are not dispatched by the user. They are predefined ahead of time (with class methods), and then dispatching the event triggers the listener. There is nowhere for the user to callonGroup() for a class-based event listener.

Due to this, there was an inconsistency where event listeners supported amessageGroup() method on the class, but all the other job types required callingonGroup() at the time of dispatch.

To help add some consistency, this PR adds support for defining amessageGroup() method on the other job types, as well. This also allows the message group logic to remain encapsulated inside of the job and not need to be provided by the dispatching logic.

Notes

• ThemessageGroup() method does not take any parameters.

• The value of the$messageGroup property takes precedence over themessageGroup() method. This allows the dispatcher to still callonGroup() and have that value used instead of themessageGroup() method.

• For notifications, the newmessageGroup() method support is in addition to the existing support for thewithMessageGroups($notifiable, $channel) method, which takes the notifiable and channel in as parameters to determine the message group.

Please let me know if you need me to make any changes or have any questions.