pingdotgg / pingdotgg/t3code

[Bug]: Long commands cause horizontal overflow in the Add Action dialog

Open Beginner friendly
#11,443 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

accepted bug via-triage
Dominant language
TypeScript
Stars
23k
Forks
5.9k
Avg merge
11h 14m
Merged PRs (30d)
357

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. Open a project in T3 Code and open Add Action.
  2. Enter a name for the action.
  3. Paste a command with a long path or argument into Command. For example, paste this as a single line:
ln -s "$HOME/Code/example-project/a-very-long-directory-name/another-long-directory-name/one-more-long-directory-name/src/config/Secrets.swift" "src/config/Secrets.swift"
  1. Inspect the dialog before saving or running the action.

I encountered this while adding a symlink command with a long file path, as shown in the screenshot.

Expected behavior

The command field and the rest of the form should stay within the dialog width, with all controls visible.

Soft word wrap in the command field could help keep long paths readable, provided it only changes the display and preserves the command text and intentional line breaks.

Actual behavior

A long command line makes the form content overflow horizontally. The right edges of the fields and helper text are clipped, controls on the right are pushed out of view, and a horizontal scrollbar appears across the bottom of the form.

This affects the layout of the whole Add Action form and makes it harder to review or configure the action.

Impact

Minor bug or occasional failure

Version or commit

Unknown; not captured in the screenshot.

Environment

macOS, T3 Code desktop app.

Logs or stack traces

Screenshots, recordings, or supporting files

Add Action dialog with horizontally overflowing fields and a scrollbar below the form

Workaround

No response

Contributor guide

Open the 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.

Research direction

Start in apps/web by locating the Add Action dialog and reproduce the issue with the long command shown in the report. Adjust the command field and form layout so the dialog stays within its width without changing command text or intentional line breaks, then verify that controls remain visible and no horizontal scrollbar appears.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.