Job arguments in dashboard?

[majkelcc]

Hi,

Migrating from Sidekiq I'm missing jobs arguments in the jobs lists. Would a PR adding them be welcomed?

While talking about jobs arguments, is there a reason to display {"attempt"=>1, "_aj_ruby2_keywords"=>["attempt"]} vs {attempt: 1}?

[bensheldon]

I'm open if you think you can make it work fitting that info into the table.

For formatting the job arguments, it hasn't been top of my priority list, so if you think you can clean it up, I'd appreciate that. The only thing I'd be worried about is making sure that we're not hiding/masking information that would be useful when debugging, or introducing any performance issues (for example, I want to avoid loading ActiveJob constants).

[majkelcc]

I'm open if you think you can make it work fitting that info into the table.

This indeed turned out to be a problem very early. I'll see what I can do.

As for the arguments, these _aj_ arguments seem to be internal to ActiveJob and there shouldn't be any harm in removing them from the view (Sidekiq is not displaying them).

(...) or introducing any performance issues (for example, I want to avoid loading ActiveJob constants)

👍