Refactor Jobs APIs in V3 #2145
Labels
enhancement
New feature or request
priority-low
Legit issue but cosmetic or nice-to-have
v4
Prospective changes for v4
Some Jobs APIs have a lot of required and optional parameters that might be better suited to be provided in an interface.
Originally raised by @zFernand0 in #2142 (comment)
However, others just log a trace and pass parameters directly to a common function (i.e.
submitJclNotify
tosubmitJclNotifyCommon
, andsubmitJob
tosubmitJobCommon
)We may want to investigate if we should change those functions in V3 to just use the same parameters as the common methods, or remove the common methods in favor of those methods.
Originally raised in #2142 (comment)
The text was updated successfully, but these errors were encountered: