Clicking a file in the dataset file tree leaves no visible trace: the picked row is never highlighted

Offen
#9,501 1 Kommentar 0 Reaktionen 1 zugewiesene Person Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

@yangzhang75 arbeitet bereits daran.

Seit 16.11.2026.

Bewertung

Dieses Issue wurde noch nicht bewertet.

Beschreibung

What happened?

user-dataset-version-filetree is the file tree every dataset and model browser uses: the versions/files browser (on the dataset page and on the model page), the dataset-selection modal and the model-selection modal. Its click handler (actionMapping.mouse.click in user-dataset-version-filetree.component.ts) toggles a folder open and, for a file, emits selectedTreeNode to the host -- and does nothing else. It never calls the tree library's TREE_ACTIONS.ACTIVATE, so the tree never has an active node, the library never marks the clicked row, and the only sign that a file was picked is whatever the host does with the event.

On the dataset and model pages the host loads the file's preview, so the click has a visible result there. In the dataset-selection modal (file mode, used to pick a file for a UDF parameter) the host only stores the path (onFileSelected sets selectedPath): the clicked row looks exactly like every other row, and the one hint that a pick happened is the Select button turning enabled. A user clicking from file to file cannot see which one is current, and clicking a file that is already picked gives no feedback at all. In the model-selection modal the tree is not even bound to a handler, so a click there does nothing visible either.

Expected: the clicked file reads as picked -- the row is the tree's active node and is drawn like a selected row elsewhere in the app (the ant blue-1 fill with a blue accent that the dashboard's list rows and the workspace's selected cards use), on every host, including a re-click of the same file.

How to reproduce?
  1. Add a CSV File Scan (any operator with a fileName property, which renders as the dataset file selector) and click its Select File button: the dataset-selection modal opens in file mode.
  2. Pick a dataset (its first version is selected for you) so the file tree shows; click a file, then another, then the first one again.
  3. No row stays highlighted after a click (only the tree library's hover tint shows while the pointer is over a row); only the Select button's enabled state changes. The tree behaves the same in the model picker, and in the UDF parameter's dataset picker (version mode, where a file click is not an answer at all and still looks like one could be).
Version/Branch

1.4.0-incubating-SNAPSHOT (main)

Commit Hash (Optional)

No response

What browsers are you seeing the problem on?

No response

Relevant log output

Vorherrschende Sprache
Scala
Sterne
333
Forks
202
Ø Merge
3 T. 11 Std.
Gemergte PRs (30 T.)
185

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus apache/texera

Alle Issues in apache/texera

Ähnliche Issues

Weitere Issues zu Scala

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.