Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

review/assess reject the vault path that next/plan/adopt just printed for the same topic

Closed
#313 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

A pull request for this has already been merged.

  • #422 by @Kuldeep2822k — merged

Assessment

Difficulty
3/5
Estimated time
Half a day
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
nodejs, typescript
Domain
cli

Research direction

The payload names no source files, so start by running palee next on a topic, then pass the printed Path: value to palee review to reproduce the exit-2 error. Find where review and assess resolve a topic argument and compare it with the path that next, plan and adopt print. Before changing code, confirm the intended lookup rules in the spec, because the issue itself says this may be a wording fix. Done means either the displayed path resolves, or the displayed text and the help output consistently say that only ID or title is accepted.

Written by the indexing model from the issue text.

Description

bug priority: low

Summary

next, plan and adopt all display a topic's vault path, but review/assess resolve only titles and IDs. Passing back the exact string the tool just printed fails.

Repro

next prints Path: w/one.md for a topic. Feeding that identifier to review:

Error: No topic found matching "w/one.md"
[exit 2]

Expected

Either accept the path the tool itself displays, or never present the path as an identifier-like token.

Confidence

Lower than the blockers in this batch — observed while verifying another finding, and not yet checked against the spec. If displaying the path is deliberate and lookups are title/ID-only by design, this should become a wording fix ("ID or title") rather than a lookup change.

Environment
  • palee 0.6.0, local build from main at 02dacd0 (installed as palee-test; reproduce with palee)
  • Node v24.19.0, Windows 11 x64, Git Bash
  • Every command was run for real; exit codes captured by command substitution (never $? after a pipe)
Dominant language
TypeScript
Stars
1
Forks
0
Avg merge
1d 8m
Merged PRs (30d)
130

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Kuldeep2822k/cli

All issues in Kuldeep2822k/cli

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.