nu_plugin_tree - competing names

[cboecking]

FYI - I had trouble installing because there exists a nu_plugin_tree in cargo (v 0.44.0). I could not get it to work since it was last touched in 2022. (https://lib.rs/crates/nu_plugin_tree)

It took me a while to realize that the above plugin was not the same as this one. After I cloned this repo and installed per your instructions, all worked as expected.

[fdncred]

Yup, very true. We used to include nu_plugin_tree with nushell, which was a little bit different from this one. You can tell by the version number 0.44.0 vs 0.105.1. So, the one in crates.io is quite old. Also, mine is not published on crates.io. I'm not sure I like the way it works. It needs some help I think.

[cboecking]

I found your plugin because I need a way to visual projects. Is there any way I can help.

Here are the details in case your interested:

• A project header has a link to its parent project (this creates a tree-like structure)
• In sql, this is a stk_project table that has a foreign key to its self (stk_project_parent_uu)

Here is my quick analysis:

Project Recursive Parent Child

The purpose of this document is to highlight options for showing recursive parent-child relationships.

ls *

Here is an example using ls **/*. Here are the details:

• This is a very 'name' based approach to trees
• Notice how child names are appended as you traverse down the tree
• This approach gives you the easy ability to show attributes with each child record (ex: type, size, modified)
• This approach is visually easy to see and interpret
• This approach is easy to filter using nushell where and string matching

~/code/chuck-stack-claude/stk-app-sql/test> ls **/*
╭────┬──────────────────────────────────────────┬──────┬─────────┬──────────────╮
│  # │                   name                   │ type │  size   │   modified   │
├────┼──────────────────────────────────────────┼──────┼─────────┼──────────────┤
│  0 │ TESTING_NOTES.md                         │ file │  9.2 kB │ a day ago    │
│  1 │ bak                                      │ dir  │  4.0 kB │ 2 weeks ago  │
│  2 │ bak/shell.alt.tcp                        │ file │  2.8 kB │ 2 weeks ago  │
│  3 │ debug-elaborate.nu                       │ file │  1.2 kB │ 3 days ago   │
│  4 │ ignoreme                                 │ dir  │  4.0 kB │ 2 weeks ago  │
│  5 │ ignoreme/new.nu                          │ file │  1.0 kB │ 2 weeks ago  │
│  6 │ ignoreme/new.sql                         │ file │   298 B │ 2 weeks ago  │
│  7 │ ignoreme/readme.md                       │ file │  2.0 kB │ 2 weeks ago  │
│  8 │ ignoreme/show.nu                         │ file │   880 B │ 2 weeks ago  │
│  9 │ ignoreme/show.sql                        │ file │   539 B │ 2 weeks ago  │
│ 10 │ pg_extension                             │ dir  │  4.0 kB │ 2 weeks ago  │
│ 11 │ pg_extension/17                          │ dir  │  4.0 kB │ 2 weeks ago  │
│ 12 │ pg_extension/17/pg_jsonschema--0.3.3.sql │ file │  1.7 kB │ 2 weeks ago  │
│ 13 │ pg_extension/17/pg_jsonschema.control    │ file │   131 B │ 2 weeks ago  │
│ 14 │ pg_extension/17/pg_jsonschema.so         │ file │  3.7 MB │ 2 weeks ago  │
│ 15 │ pg_extension/17/readme.md                │ file │  1.9 kB │ 2 weeks ago  │
│ 16 │ shell.nix                                │ file │  4.0 kB │ a day ago    │
│ 17 │ start-test.nu                            │ file │ 10.3 kB │ a day ago    │
│ 18 │ stop-test.nu                             │ file │   952 B │ a day ago    │
│ 19 │ suite                                    │ dir  │  4.0 kB │ 17 hours ago │
│ 20 │ suite/test-all.nu                        │ file │  2.4 kB │ 5 days ago   │
│ 21 │ suite/test-elaborate.nu                  │ file │  4.6 kB │ 17 hours ago │
│ 22 │ suite/test-event.nu                      │ file │  9.3 kB │ a day ago    │
│ 23 │ suite/test-item.nu                       │ file │  8.8 kB │ a day ago    │
│ 24 │ suite/test-lines.nu                      │ file │  6.0 kB │ 18 hours ago │
│ 25 │ suite/test-project.nu                    │ file │ 15.0 kB │ a day ago    │
│ 26 │ suite/test-request.nu                    │ file │  8.6 kB │ a day ago    │
│ 27 │ suite/test-simple.nu                     │ file │   680 B │ a day ago    │
│ 28 │ suite/test-todo.nu                       │ file │  9.0 kB │ a day ago    │
├────┼──────────────────────────────────────────┼──────┼─────────┼──────────────┤
│  # │                   name                   │ type │  size   │   modified   │
╰────┴──────────────────────────────────────────┴──────┴─────────┴──────────────╯

nu_plugin_tree

This is a recent plugin: https://github.com/fdncred/nu_plugin_tree (not from cargo install)

What normally be:

~/code/nu_plugin_tree> scope commands | where name == with-env
╭───┬──────────┬──────────┬────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┬─────╮
│ # │   name   │ category │                                                         signatures                                                         │ ... │
├───┼──────────┼──────────┼────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┼─────┤
│ 0 │ with-env │ env      │ ╭─────┬──────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮ │ ... │
│   │          │          │ │     │ ╭───┬────────────────┬────────────────┬──────────────┬─────────────┬────────────┬────────────────────────┬─────╮ │ │     │
│   │          │          │ │ any │ │ # │ parameter_name │ parameter_type │ syntax_shape │ is_optional │ short_flag │      description       │ ... │ │ │     │
│   │          │          │ │     │ ├───┼────────────────┼────────────────┼──────────────┼─────────────┼────────────┼────────────────────────┼─────┤ │ │     │
│   │          │          │ │     │ │ 0 │                │ input          │ any          │ false       │            │                        │ ... │ │ │     │
│   │          │          │ │     │ │ 1 │ variable       │ positional     │ any          │ false       │            │ The environment        │ ... │ │ │     │
│   │          │          │ │     │ │   │                │                │              │             │            │ variable to            │     │ │ │     │
│   │          │          │ │     │ │   │                │                │              │             │            │ temporarily set.       │     │ │ │     │
│   │          │          │ │     │ │ 2 │ block          │ positional     │ closure()    │ false       │            │ The block to run once  │ ... │ │ │     │
│   │          │          │ │     │ │   │                │                │              │             │            │ the variable is set.   │     │ │ │     │
│   │          │          │ │     │ │ 3 │                │ output         │ any          │ false       │            │                        │ ... │ │ │     │
│   │          │          │ │     │ ╰───┴────────────────┴────────────────┴──────────────┴─────────────┴────────────┴────────────────────────┴─────╯ │ │     │
│   │          │          │ ╰─────┴──────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯ │     │
╰───┴──────────┴──────────┴────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┴─────╯

Turns into:

~/code/nu_plugin_tree> scope commands | where name == with-env | tree
root
├── name
│   └── with-env
├── category
│   └── env
├── signatures
│   └── any
│       ├── parameter_name
│       │   └── null
│       ├── parameter_type
│       │   └── input
│       ├── syntax_shape
│       │   └── any
│       ├── is_optional
│       │   └── false
│       ├── short_flag
│       │   └── null

[cboecking]

One thing that is interesting about my requirement is that any given sub-project might have lines. This means that the visualization will be a tree where each node will have zero to many lines (table or lines).

This speaks to your visualization in issue #1 .

[fdncred]

Is there any way I can help.

Sure. You can submit PR(s) to help add the functionality you're looking for.

I'd definitely like to have a --path flag (or something similar) that demonstrates a traditional directory hierarchy vs a nushell value hierarchy.

I'd also be down with just about any other visualization that could be added.