Darren Schroeder
Darren Schroeder
> And how do I remove the {record 0 fields} ... Right now the only way to do this is with the udpate command updating each item with null.
Sure. Here's a quicky. There may be other ways of doing it too. ### Before ```nushell ❯ { args: {} data: 'hi there' files: {}} ╭───────┬───────────────────╮ │ args │ {record...
Have you looked at `items`? ```nushell ❯ { args: {} data: 'hi there' files: {}} | items {|key value| $'($key)-($value)'} ╭───┬───────────────╮ │ 0 │ args-{} │ │ 1 │ data-hi...
I'm not sure if there's an easy way to do that. I believe you'd have to know the structure of the data and go through each item like this. ```nushell...
I wonder if this is because we allowed the only NU_LIB_DIRS folder to be commented out in the env.nu?
I submitted a PR yesterday where `$env.NU_LIB_DIRS` will be set by default again in our next release.
> Because nushell's vscode plugin can not recognize the need to source files from the scripts directory through env.nu, this can cause the plugin to report a error File not...
I think we could have both of those paths in NU_LIB_DIRS, but the vscode extension needs to have those defined inside of its settings too.
> iff $nu.default-config-dir | path join script as the default configuration in vscode extension. There is no default configuration for the vscode extension. Feel free to PR such a thing...
Yes, include dirs is one of the options in the vscode nushell extension. iirc, it populates NU_LIB_DIRS and helps make finding things easier for the extension. I have 5 folder...