You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For consistency, inside a given project, we should either define childspecs inside workers, or inside supervisors. That doesn't mean there aren't exceptions to the rule, but that's why rules are configurable :)
This should support option ignore.
Of course, a supervisor might supervise other supervisors, so we need to take care of that case. In any case, the goal should be to "have the childspec defined in the module that uses it" v. "have the childspec defined outside the module that uses it".
I'm not sure about the default in (see below): supervisor v. worker.
I propose [{elvis_style, childspecs, #{ in => supervisor, ignore => [] }.
The text was updated successfully, but these errors were encountered:
For consistency, inside a given project, we should either define childspecs inside workers, or inside supervisors. That doesn't mean there aren't exceptions to the rule, but that's why rules are configurable :)
This should support option
ignore
.Of course, a supervisor might supervise other supervisors, so we need to take care of that case. In any case, the goal should be to "have the childspec defined in the module that uses it" v. "have the childspec defined outside the module that uses it".
I'm not sure about the default
in
(see below):supervisor
v.worker
.I propose
[{elvis_style, childspecs, #{ in => supervisor, ignore => [] }
.The text was updated successfully, but these errors were encountered: