Wondering whether it'd be more correct to rename the --asJob command param to allude to walk methods being run as queued jobs, rather than as "a job"... since there could be [many] more than one job, and the salient feature is that the methods get queued (rather than running right away). Should the naming of this param more emphasize the involvement of the "Queue" rather than the nature of being run as "job(s)"?
Some possible alternatives:
--queue, --withQueue, --useQueue, --inQueue, --enqueue
Opine.
Wondering whether it'd be more correct to rename the
--asJobcommand param to allude to walk methods being run as queued jobs, rather than as "a job"... since there could be [many] more than one job, and the salient feature is that the methods get queued (rather than running right away). Should the naming of this param more emphasize the involvement of the "Queue" rather than the nature of being run as "job(s)"?Some possible alternatives:
--queue,--withQueue,--useQueue,--inQueue,--enqueueOpine.