diff options
| author | Christophe Besson <cbesson@gmail.com> | 2026-08-15 09:50:53 +0200 |
|---|---|---|
| committer | Christophe Besson <cbesson@gmail.com> | 2026-08-15 09:50:53 +0200 |
| commit | 4c4fe55bc17ea2223a52b31d2be5b762af8d75bf (patch) | |
| tree | b41bb71cce5241b462c1640dbfcc88f7ac6c3f8e /docs/meshbay-draft-v5.md | |
| parent | 4fa546a759dc9bd2ab77f793e3f2e660acd31bdb (diff) | |
| download | meshbay-4c4fe55bc17ea2223a52b31d2be5b762af8d75bf.tar.gz | |
fix(cli): --group takes a name, and operator pair says it takes none
Two ways the CLI misled someone attaching a second group to a node.
`meshbay-node operator pair --group grenet` accepted the flag and ignored
it: pairing is node-wide and always was. That invites exactly the wrong
reading — that a code belongs to a group, and that pairing had failed
because the group did not change. It now refuses the flag and says one
paired browser covers every group the node hosts.
`--group` also only ever accepted a UUID. A name went through untouched
and the daemon answered as though the group did not exist, which is not
what happened. It now resolves a name against node.toml, and when there
is no match it prints the groups there are, with their ids — the missing
half of the answer.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Diffstat (limited to 'docs/meshbay-draft-v5.md')
0 files changed, 0 insertions, 0 deletions