-
-
Notifications
You must be signed in to change notification settings - Fork 0
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's an issue with clicking on 'projects' in the breadcrumb trail, the part of the file browser that shows the path separated by '>' and lets you click up the folder structure. If you click on 'projects', the API is returning the new error about not being allowed to access that folder, but the frontend doesn't handle that error in any way, and the file browser gets stuck at 'Loading files'.
Ideally, the breadcrumb trail would not show you a folder level that you're not allowed to select - the first item would be . That way, users aren't even aware that there's a folder they can't access. If for some reason that proves overly difficult to implement, then the file browser should catch the new error that the API is returning, remove the loading message, and probably make a notification that that folder is inaccessible.
7dfa35f
to
07aa584
Compare
Summary
Do not allow to explore all directories in the file browser panels.
Suppress going back when exploring particular project.
Also allow configuring the top limit
References
closes #9220
closes #9221
QA Steps
Back button not present when in the selected project
Back button is shown when we go atleast one folder deep
Same for studio