api.fs.create_directory

[thepenguinthatwants]

Right now

• type 'a' to add a file

Could be nice if

• type 'A' to add a folder

[kyazdani42]

type a and then add a trailing / will create folders (see #3).
If you really want a command to do that, please reopen this :)

[twiddli]

Hi, great plugin but I think this is a bit unintuitive for new people (like me).
It would be great to have a dedicated command for it as well. That would at least save people from having to google.

I have been trying to match Vim's default file explorer's keymappings and would really like to dedicate d to creating folders.

[alex-courtis]

We can do this. Something like:

fs.create_directory({node})              *nvim-tree-api.fs.create_directory()*
    Prompt to create a directory.

    Parameters: ~
      • {node} (Node) parent, uses the parent of a file.

[gegoune]

On Unix systems directory is just a type of node, same as file. Should we make it more generic, like create_node?

[alex-courtis]

On Unix systems directory is just a type of node, same as file. Should we make it more generic, like create_node?

Yes. We could be more generic and extend the existing create like:

fs.create({node}, {opts})                          *nvim-tree-api.fs.create()*
    Prompt to create a file or directory. Use a trailing `/` for a directory.

    Parameters: ~
      • {node} (Node) parent, uses the parent of a file.
      • {opts} (table) optional parameters

    Options: ~
      • {type} (string) `"file"` or `"directory"`, default `"file"`

Only problem is how we would pass those opts in, with the node populated. Passing nil would work, we'd need to note it in the doc.

[alex-courtis]

If I were designing the API from scratch today, I'd make the {node} optional parameters for all such functions. Node really optional.

e.g.

fs.create({opts})                                  *nvim-tree-api.fs.create()*
    Prompt to create a file or directory. Use a trailing `/` for a directory.

    Parameters: ~
      • {opts} (table) optional parameters

    Options: ~
      • {node} (Node) default node under cursor
      • {type} (string) `"file"` or `"directory"`, default `"file"`

The problem is backwards compatibility. It was achieved for functions like ApiTreeToggleOpts via looking at parameter types. We can't do that in this case as node and opts are both tables.

One option is to look for fields like absolute_path, fs_stat etc. in the table parameter, to determine whether it is a node or opts. Not a great solution.

[alex-courtis]

Created #2146

[alex-courtis]

We have a functional workflow for adding directories via the trailing /.

I'm not seeing much value here...

@gegoune ?

[gegoune]

Personally I am not that bothered either. / suffix is what I use every time I need to create directory.

This is an old issue that Kiyan closed promptly. Also premise that "That would at least save people from having to google." isn't entirely true if documentation is provided with plugin itself (it is).