Autoload Activejob::Arguments

[alpaca-tc]

Summary

Currently, initial rails console can't load ActiveJob::Arguments.

$ ./bin/rails console
> ActiveJob::Arguments.serialize(...)
NameError: uninitialized constant ActiveJob::Arguments

It is inconvenient for me because I want to check the behavior from the console.

[rails-bot]

Thanks for the pull request, and welcome! The Rails team is excited to review your changes, and you should hear from @schneems (or someone else) soon.

If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.

This repository is being automatically checked for code quality issues using Code Climate. You can see results for this analysis in the PR status below. Newly introduced issues should be fixed before a Pull Request is considered ready to review.

Please see the contribution instructions for more information.

[y-yagi]

Activejob::Arguments is not a public API. Why would you want to use it directly?

[kamipo]

I regarded this PR as the fixing dependency.
ActiveJob::Arguments is used internaly in some files (e.g. Core, TestHelper), but looks like these doesn't work unless after ActiveJob::Base is loaded (ActiveJob::Base requires active_job/enqueuing and active_job/execution which includes require "active_job/arguments").

[rafaelfranca]

Yeah, this PR make sense only because we were missing the requires in but now it seems broken because Arguments will not be eagerloaded when the application is eagerloaded. We need to fix that.

[rafaelfranca]

Probably that is also a problem with Serializers and other constants, we need to review the eager loading of Active Job.