yeppog / ped Goto Github PK

Currently, truncation with ellipsis is used to handle overflows, but this is a huge bug to the user as the user is unable to see the entire phrase if it happens to be long.

When exporting the csv, the console shows that it is saved in test.csv, however, does not specify the proper directory. Since keying in test.csv when importing means that the file is taken from the current directory, the console output should also indicate that it is saved in the data folder.

When there are two instances of LingoGO open, only one instance has its changes saved.

In slideshow mode, list mode commands are disabled, hence should immediately show a message that it is unavailable, rather than telling the user that the command format is invalid.

When exporting the data with erroneous file name as shown below, FileNotFoundException is not handled properly.

When a buggy .csv is used, cards are imported up till the first buggy input, but the console does not tell the user so, nor does the documentation do so. This behavior or the supposed behavior should be properly documented.

The json keys are of the correct format, but LingoGO refuses to read anything when there is a null value in one of the keys.

As a user, I might be confused as to why this is an invalid command format, rather than an invalid file input. I would suggest the message to show the correct error.

Windows contain reserved file names that cannot be used, and this error is not being handled for the user to see.