You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When typing cd from the initial state, the error message recieved is "provided path cannot be resolved against the current path".
Above is what I would expect the behaviour to be, similar to how the CLI works. It should ideally not throw an error message to the user, when in fact the command entered is valid.
In our application ~ is both our root directory as well as home directory. We used the term root directory to inform users that there is no directory above it.
At the same time we wanted to give more descriptive message to explain why the command does not achieve any results as compared to the CLI.
As mentioned in UG, there is no directory above the root directory, the only navigable directories are root and group, and hence trying to navigate above it shows an error message.
In this case of unix, we are unsure if cd .. at the root directory is a valid command, but in our application we decided to make it an invalid command and made it clear in the UG, and hence decided an invalid command should have an error message shown.
When typing cd from the initial state, the error message recieved is "provided path cannot be resolved against the current path".
Above is what I would expect the behaviour to be, similar to how the CLI works. It should ideally not throw an error message to the user, when in fact the command entered is valid.
[original: nus-cs2103-AY2324S1/pe-interim#6034] [original labels: severity.Low type.FeatureFlaw]
The text was updated successfully, but these errors were encountered: