Hub CLI Issues (due to no frontend)
Open
needs planning
- Dominant language
- TypeScript
- Stars
- 280
- Forks
- 132
- Avg merge
- 5d 18h
- Merged PRs (30d)
- 8
Description
- Need special knowledge to know which LSP to choose - suggestions are ordered by priority, do not open 2 channels with the same LSP - can some of this be moved to the hub backend so it just returns 1 best suggestion rather than the whole suggestions list (which contains suggestions for ALL networks)?
- Node sync is problematic because it only happens once per hour if frontend is not open on the node page. This doesn't work well at all for CLI. Rather than queuing a sync (current option), we should consider having a call to sync in a blocking way so the CLI doesn't get stuck / have to poll.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.