Show extension dialogs inline in the chat, not as a popup
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- typescript
- Domain
- frontend
Research direction
Start by reviewing the chat-ask PR and how extension dialogs currently open as popups. Decide which presentation to use: inline prompts persisted until answered, a hideable popup, or a side panel. Then implement the chosen form, including persistence and transcript recording if inline, and add browser tests that verify the chosen behavior and confirm the old popup behavior is gone.
Written by the indexing model from the issue text.
Description
Problem
Extension dialogs (confirm, choose, text prompts from extensions) still open as a popup over the whole page. Without context they can be confusing, especially when one opens out of nowhere while the person is somewhere else in the chat.
The agent's ask_question questions are being moved inline and kept on the server (see the chat-ask PR). Extension dialogs stay popups until we decide how they should look.
Open question
Should extension dialogs also show inline above the composer, like questions, or does a popup fit them better? Options to weigh:
- Inline in the chat, kept on the server until answered, the same as questions.
- A popup that can be hidden and reopened from the chat.
- A separate side panel for prompts (probably too much).
Scope when decided
- Same persistence and transcript record as questions, if inline.
- Browser tests for the chosen form, and a check that the old popup behaviour is gone.
- Dominant language
- TypeScript
- Stars
- 297
- Forks
- 81
- Avg merge
- 8h 47m
- Merged PRs (30d)
- 167
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from thecodacus/pithagoras
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
thecodacus/pithagoras#364 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
thecodacus/pithagoras#306 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
thecodacus/pithagoras#43 · 2 comments ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 6/100
thecodacus/pithagoras#361 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 32/100
thecodacus/pithagoras#347 ·
Maintainers usually reply within 1 day
All issues in thecodacus/pithagoras
Similar issues
-
needs-area-label
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
liberation-data/drivine#615 ·
Maintainers usually reply within 1 day
-
backend bug ready-for-agent
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
geolens-io/geolens#3639 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
radius-project/ai-extensions#1196 ·
Maintainers usually reply within 1 day
-
good first issue
Difficulty 1/5 1-3 hours Newbie friendliness 88/100