[5.5] definition for Job interface

[Artistan]

defining methods available via @mixin

also "patch" for 5.5 to show that getJobId() is standard, 5.6 includes the methods.

#21298
#21303

[sisve]

This looks really weird.

Why should the abstract Job class be involved with the interface? What does this give?

The getJobId is documented to return an int, but a majority of the implementations states it returns a string. And in the case of DatabaseJob it requires that the actual job uses the InteractsWithQueue trait or the method will throw an exception.

Should the getJobId really be declared on the interface if not all implementations have a working method implemented out-of-the-box?

[Artistan]

here is my reasoning .

• every instance in the framework of extends Job has the method
• I do not see where database will throw exception, it has the method also.
  https://github.com/laravel/framework/blob/5.5/src/Illuminate/Queue/Jobs/DatabaseJob.php#L86
• based on research I have done, each of those ids should actually be int
• the interface is what is used in the Jobs created by users
• without the mixin in the interface/contract there is no definition of or reference to what the job methods actually are
• this improves readability and navigation for the users tracing the job contract to where the implementation actually is.

this is already implemented for 5.6.