Skip to content

fix: sibling detection false positive when prefix#152

Merged
Revxrsal merged 3 commits intoRevxrsal:v4from
SkytAsul:v4
Feb 6, 2026
Merged

fix: sibling detection false positive when prefix#152
Revxrsal merged 3 commits intoRevxrsal:v4from
SkytAsul:v4

Conversation

@SkytAsul
Copy link
Contributor

@SkytAsul SkytAsul commented Feb 1, 2026

Examples of fixed siblings:

  • bq help has siblings bq test AND bquests test, since bquests starts with bq (but it's a coincidence). This has been fixed by changing the siblingPath from a simple String to an array of Strings.
  • bq help has sibling someCommand [something] since initially the siblingPath of someCommand [something] was the empty string. This has been fixed by setting the siblingPath to the first node literal when it only contains one (so, when the command is a "top-level" command).

This closes #114.

SkytAsul added a commit to SkytAsul/BeautyQuests that referenced this pull request Feb 1, 2026
Closes #381. Requires Revxrsal/Lamp#152 to be merged for this to function properly.
e.g. `bq help` has siblings `bq test` AND `bquests test`, since `bquests` starts with `bq` (but it's a coincidence)

This also fixes Revxrsal#114.
@Revxrsal Revxrsal merged commit 1ff4f27 into Revxrsal:v4 Feb 6, 2026
1 of 2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Command Resolution Issue: Sibling and Related Commands Not Properly Resolved in Split Command Registrations

2 participants