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

[Bug]: Android project paths wrap in the new-task picker

Open Beginner friendly
#14,177 0 comments 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
72/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
mobile

Research direction

Start in the apps/mobile Android project and trace the New thread → Choose project picker where workspace paths are rendered. Reproduce with a long Windows workspace path, then verify paths stay on one line with middle ellipsis and project rows retain a consistent height.

Written by the indexing model from the issue text.

Description

Area

apps/mobile

Description

On Android, long workspace paths in New thread → Choose project wrap onto a second line. This makes affected rows taller than rows with short paths and makes the project list harder to scan.

Steps to reproduce
  1. Connect the Android app to a Windows environment.
  2. Add a project with a long workspace path.
  3. Tap New thread.
  4. Open Choose project.
Expected behavior

Project paths stay on one line and use middle ellipsis so both the drive/root and final folder remain recognizable. Project rows keep a consistent height.

Actual behavior

Long paths wrap to two lines and increase the row height.

Environment
  • T3 Code Android 1.3.0 (versionCode 57)
  • Samsung Galaxy S25 Ultra (SM-S9380)
  • Android 16
  • Windows remote environment
Before

Long project path wrapping onto a second line

After (local fix)

Long project path kept on one line with middle ellipsis

Dominant language
TypeScript
Stars
23.6k
Forks
6.1k
Avg merge
10h 20m
Merged PRs (30d)
309

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.