getappmap / getappmap/appmap-js

Make `@`modes sticky

Open
#1,963 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

navie-plan
Dominant language
TypeScript
Stars
53
Forks
18
Avg merge
3d 18h
Merged PRs (30d)
8

Description

Currently @mode is lost when continuing conversation which risks losing features such as fetching source files and detailed diagram prompting. It would be nice if it was sticky, ie. after a prompt gets sent let the mode stay in the prompt box. For extra nice UX it could be in a pill that can be single-backspaced.

The first part of this implementation is in the CLI / RPC. The explain response should indicate clearly what the command mode of the user message was (explicitly stated or implicitly assigned).

If Navie is not clearly indicating implicit command modes back to the caller, this should be added and used by the CLI / RPC

The second part of this implementation is in the UI Vue components, specifically in the search box in which the user types their question.

For follow up questions, the text input should be preloaded with the command prefix of the most recently asked question (whether explicit or implicit).

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

Start with the CLI/RPC explain response and verify whether it clearly reports the explicit or implicit command mode. Then inspect the Vue search box components and follow-up prompt flow. Done means the latest command prefix is retained in the input, with the proposed pill/backspace behavior if feasible, and explicit or implicit modes are consistently surfaced by the CLI/RPC.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
api, cli, frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.