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
run* was kind of unnecessary and contributors are not inclined to use it. Maybe it somewhat useful to distinguish effects from functions that generate bash commands, like ssh. This could would be better achieved with a namespace, e.g. commands.ssh.
Another potential issue is the the verb is not always fixed. Behavior may vary by branch, which is represented either by runIf(?: #65 ) or by a parameter like runNixOpsaction = "switch". In the latter case, for which runIf is not suitable, what should the effect function be called? nixops is kind of taken by the package name, but that's not an issue when users call it as effects.nixops { action = _some logic_; }
The text was updated successfully, but these errors were encountered:
run*
was kind of unnecessary and contributors are not inclined to use it. Maybe it somewhat useful to distinguish effects from functions that generate bash commands, likessh
. This could would be better achieved with a namespace, e.g.commands.ssh
.Another potential issue is the the verb is not always fixed. Behavior may vary by branch, which is represented either by runIf(?: #65 ) or by a parameter like
runNixOps
action = "switch"
. In the latter case, for whichrunIf
is not suitable, what should the effect function be called?nixops
is kind of taken by the package name, but that's not an issue when users call it aseffects.nixops { action = _some logic_; }
The text was updated successfully, but these errors were encountered: