[Bug]: Add environment dialog gives no feedback after clicking Add; environment is added but dialog stays open

Open Beginner friendly
#31,718 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
67/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
desktop

Research direction

Start in apps/web and trace the SSH card's Add environment dialog from its submit handler through the connection flow. Check how the dialog handles pending, success, and error states; done means it gives visible progress, closes after success, and shows an error on failure. The issue does not name a test, so locate the relevant dialog or environment tests and run them.

Written by the indexing model from the issue text.

Description

Before submitting
  • I searched existing issues and did not find a duplicate.
  • I included enough detail to reproduce or investigate the problem.
Area

apps/web

Steps to reproduce
  1. Desktop app: Settings > Environments > Add environment.
  2. Choose the SSH card and enter a host that works.
  3. Click "Add environment" in the dialog.
Expected behavior

The dialog shows that the click was accepted. It shows progress while the environment connects. It closes on success or shows an error on failure.

Actual behavior

Nothing visible happens after the click. The dialog stays open and shows no progress, no success message, and no error. The environment is added anyway. The new entry appears only after I close the dialog by hand. A second click on the button might add the same environment twice, because nothing shows that the first click worked. I did not test that.

Notes
  • Happens with the SSH card. I did not test the Remote link card.
  • The desktop app version was not recorded.
Dominant language
TypeScript
Stars
24.8k
Forks
6.4k
Avg merge
20h 2m
Merged PRs (30d)
164

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

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 pingdotgg/t3code

All issues in pingdotgg/t3code

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.