Closed soc-se-bot closed 2 years ago
Maybe we can make it so that, import and export if specified pathfile use the pathfile instead of bringing up the FileChooser.
Will the additional implementation be affected under feature freeze? I feel that the advantages of allowing the user to select the dataPath via GUI far outweigh the advantages of allowing users to input the dataPath themselves.
Pros
/Users/*****/Library/CloudStorage/OneDrive-NationalUniversityofSingapore/Y2S2/CS2103/Projects/TP/build/libs/data/trackermon.json
Cons
What does everyone think?
Can't you just implement in the way Jon suggested instead of comparing them and doing one only? That way you can the best of both worlds.
I think we are not allowed to implement the import/export allowing users to add in a file path for fast typist due to the feature freeze. I guess this can be implemented in the future instead and just acknowledge this as an issue.
We've noted the benefits of allowing users to provide a dataPath via CLI, but due to the constraints of v1.4's feature freeze, we'll postpone the implementation to a later date.
The import and export features require the user to select the file to import from or export to via the GUI, without an option to specify the file via the CLI.
This makes importing and exporting troublesome for fast typists.
Labels:
severity.Medium
type.FeatureFlaw
original: Ashuh/ped#1