SharedDirectoryMoveResponse#1074
Conversation
| } else if (clipboardError) { | ||
| errorText = clipboardState.errorText || 'clipboard sharing failed'; | ||
| } else if (unknownConnectionError) { | ||
| errorText = 'Session disconnected for an unknown reason'; |
There was a problem hiding this comment.
| errorText = 'Session disconnected for an unknown reason'; | |
| errorText = 'Session disconnected for an unknown reason. Try reloading (or refreshing) the browser.'; |
and then the button could say Reload or Refresh?
also i'm confused whether our error messages should be all lower cap or properly capitalized with punctuation. I'm just seeing a mixture of both. It's not a big deal to me but just wondering in general
There was a problem hiding this comment.
also i'm confused whether our error messages should be all lower cap or properly capitalized with punctuation.
In my opinion if we're displaying it as a message to the user, we should strive to give it proper capitalization and punctuation.
| } | ||
|
|
||
| // | message type (24) | completion_id uint32 | err_code uint32 | | ||
| encodeSharedDirectoryMoveResponse(res: SharedDirectoryMoveResponse): Message { |
There was a problem hiding this comment.
What do you think of an declarative approach for encoding similar to #1003 (comment)
There was a problem hiding this comment.
Great idea. I've added it as an issue: https://github.com/gravitational/webapps/issues/1087
* `SharedDirectoryInfoResponse` (#996) * `SharedDirectoryListRequest` (#999) * `SharedDirectoryListResponse` (#1000) * `SharedDirectoryReadRequest` (#1003) * `SharedDirectoryReadResponse` (#1005) * `SharedDirectoryWriteRequest` (#1007) * `SharedDirectoryWriteResponse` (#1008) * Tidy up `sharedDirectoryManager` (#1010) * `SharedDirectoryMoveRequest` (#1045) * `SharedDirectoryMoveResponse` (#1074) * `SharedDirectoryCreateRequest` and `SharedDirectoryCreateResponse` (#1090) * SharedDirectoryDeleteRequest and SharedDirectoryDeleteResponse (#1096) * Add warning dialog for unsupported browsers for directory sharing (#1110) * updates yarn.lock
Unfortunately when doing research for this feature, I failed to notice that the browser API I was planning to use for moving files and directories was unfinished #1064.
In the meantime, I've decided to make all error notifications show up in a modal (instead of a banner), and make a distinction between fatal and non-fatal errors, with non-fatal errors being displayed as a dismissible modal
and fatal errors showing up as a modal with a button that allows you to refresh the page
(See the video at the very bottom of this description for the modals in action).
Playback is currently unaffected by these changes, because directory sharing events are not captured or played back, the only non-fatal error is thrown by a directory sharing message. When this changes, we may need to refactor the playback system to handle non-fatal errors accurately.
Requires backport to v9/v10
closes #615
How to test manually
webappstruewebapps/packages/teleport/src/config.ts
Line 32 in becfad3
yarn start-teleport --target=https://ec2-35-171-27-185.compute-1.amazonaws.com/What to expect
Go to the top right
...menu and clickShare Directory(X-out of the "uncaught exception" screen if you get it). The directory you select should show up in the File Explorer as a shared drive
The drive should be navigable as well should any folders within it
Try moving the file from one folder in the shared directory to another, and you should see something like
sd-move-response.mov