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
It would be nice if the functions under cobra-run, are split-off into a separately exported functions.
That allows custom go tooling, to call the functions (and send them their args), as well.
Which would now basically require writhing custom variants/copies of those run sections.
Its a relatively minor change to tooling, but significantly increases usability.
I'm okey with sending in the PR myself btw :)
Note, i'm aware there is more to things at times than just the run section, primarily setting/getting of flags, but thats relatively manageable in scope compared to the, sometimes extensive, run sections
The text was updated successfully, but these errors were encountered:
Do you mean exporting the subcommands of the program? I'm not sure if this is a good idea because it's very program specific functions and they're mostly just calling the exported functions from the pkg directory anyway. Maybe if you can state your use case for it might give me better explanation because I don't quite understand your request tbh.
We're moving some tooling from bash to go.
But we've since gone over it more completely and you're correct: it wouldn't really solve much at all, as everything is too interconnected. A simple export wouldn't do anything of relevance!
It would be nice if the functions under cobra-run, are split-off into a separately exported functions.
That allows custom go tooling, to call the functions (and send them their args), as well.
Which would now basically require writhing custom variants/copies of those run sections.
Its a relatively minor change to tooling, but significantly increases usability.
I'm okey with sending in the PR myself btw :)
Note, i'm aware there is more to things at times than just the run section, primarily setting/getting of
flags
, but thats relatively manageable in scope compared to the, sometimes extensive, run sectionsThe text was updated successfully, but these errors were encountered: