maxgodfrey2004 / go-file-manager Goto Github PK

The current functionality of the Explorer class is incredibly limited. Directories may only be moved one at a time.

As such, it would be nice for the user to move through an entire path with one command. This would make the application easier to use.

When the application is run on Windows 10, the ../ symbol is treated as a file as opposed to a directory.

It may be in the user's interest to move to an absolute path. These may be identified by a leading ~ or /.

It would be nice for the Explorer type to support this functionality.

After running the repository through a go report card, it seems that not using gofmt has had some repercussions on the quality of my code.

As such, run gofmt on each file in the repository and change them accordingly.

Currently, all logic within the package fileutils is done through the type explorer. It is intended that all future developments to the package will add to the functionality of the explorer type and consequently not result in the creation of any new types.

As a result, it makes sense to rename the fileutils package to explorer; and rename all functions affixed with explorer such that the word no longer exists in their identifiers. This would make for more intuitive code.

When entering a directory whose length of contents is greater than the terminal's back buffer height in characters, the first line of text is not rendered.

It seems that it is shown one line above where textrender starts writing to the console. To see the selected file or directory, the down arrow must be pressed once, but this still prevents the user from seeing the . at the top of every directory they visit.