Versatile tree-viewer/filebrowser widget, built on top of regular-table
BSD-3-CLAUSE License
Published by telamonian over 3 years ago
open
delete
copy
cut
paste
rename
Subject<T extends IContentRow>
object (from the rxjs
lib), where T
is the "row type", which contains all of the fields needed to hold the displayed data for a single row.Subject
will generally either operate on a single T
, or a T[]
. Here's the general pattern for how external code can interact with a Subject
:
trigger command foo
on row bar
:
// supply the `next` value of the Subject
fooSub.next(bar);
Participate in implementation of command foo
:
// supply a callback; will trigger on every call of `.next(bar)`, with `bar` as the first arg
fooSub.subscribe(row => {// arbitrary code goes here});
openSub.next(bar)
is called, the tree-finder
internals will automatically trigger the "open dir" UI action, if bar
is a dir. Any other callbacks subscribed to openSub
will also run (execution order is not guaranteed, and should not be relied upon).Subjects
should actually live in the codelib/
(which contained the transpiled .js
srcs and the .d.ts
declarations) has been removed in favor of types/
(which contains the .d.ts
declarations and the .d.ts.map
declaration maps)
.js
sources have been removed from the dist (you only actually need the dist/tree-finder.js
bundle, after all), and the .d.ts.map
maps are now generated and included. This seems to result in overall better go-to-the-original-ts-srcs behavior in vscode, devtools, and possibly other tools.Published by telamonian over 3 years ago
regular-table
to v0.3.0. The previous two versions of tree-finder
(v0.0.9-0.0.10) were technically broken without a yarn link
to a local copy of regular-table
at HEAD. This dep bump sets that right.regular-table
upgrade, the elements now support a "virtual_mode" opt that changes the scrolling virutalization behavior of the grid