Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[feat]: add actions for interactive clboss commands #57

Open
chrisguida opened this issue Jul 28, 2022 · 5 comments
Open

[feat]: add actions for interactive clboss commands #57

chrisguida opened this issue Jul 28, 2022 · 5 comments
Assignees
Milestone

Comments

@chrisguida
Copy link
Contributor

see https://github.com/ZmnSCPxj/clboss#operating for all commands

clboss-status: taken care of here, but could also be its own action: #56
clboss-externpay, clboss-ignore-onchain, clboss-notice-onchain, clboss-unmanage can all be actions
clboss-swaps: could be an action or a section in properties

@kn0wmad
Copy link
Contributor

kn0wmad commented Nov 2, 2022

I would very much like an option to tell clboss to ignore certain channels - not sure if this is best as an action or as a config input

@chrisguida
Copy link
Contributor Author

chrisguida commented Nov 2, 2022

you can do this already in Spark: https://github.com/ZmnSCPxj/clboss#clboss-unmanage

but yes, it would probably be better as an action

@kn0wmad
Copy link
Contributor

kn0wmad commented Nov 2, 2022

I know it has commands, I'm saying for the UI. I kinda like the idea of having a section in the config for 'ignored' where you can just add the channels or peers to ignore

@chrisguida
Copy link
Contributor Author

You mean you want this as config options as opposed to actions?

@kn0wmad
Copy link
Contributor

kn0wmad commented Nov 3, 2022

I think I'd prefer that, but I'm not entirely convinced of that position, just putting the opinion out there. You know the ecosystem better

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Todo
Development

No branches or pull requests

2 participants