pingdotgg / pingdotgg/t3code

Grouped project icon differs between settings and sidebar

Open
#11,835 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

Update: local case resolved

After pulling the commit containing t3.json and the favicon into the Windows checkout, then fully closing and reopening T3 Code, the sidebar now shows the correct icon.

I can no longer reproduce the mismatch. I didn’t test pulling and restarting separately, so I can’t tell which step resolved it. The source-selection difference noted below remains, but this case no longer demonstrates an ongoing bug.

Original report

With the same repository grouped across two connected environments, project settings shows the automatic favicon while the desktop sidebar shows a generated monogram.

Settings selects the first connected group member, whereas the sidebar prefers the primary environment. Executing those selection expressions with two connected members reproduces the different choices.

Expected: the group’s settings preview and sidebar agree on its icon.

The selection mismatch exists in upstream commit 5ea6439816470288d3f2b6b43635fea41fbbb101. The reason the local checkout returns a fallback has not yet been established.

Related: #7464, closed unmerged. This report concerns the inconsistent group preview, without proposing cross-client caching or retry machinery.

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 by comparing the settings preview and desktop sidebar selection expressions described in upstream commit 5ea6439816470288d3f2b6b43635fea41fbbb101, using two connected group members. Verify whether the local fallback is still reproducible after pulling t3.json and the favicon and restarting T3 Code; done means both views select the same icon source.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.