This PR has 42 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

Label      : Extra Small
Size       : +42 -0
Percentile : 16.8%

Total files changed: 2

Change summary by file extension:
.cs : +33 -0
.resx : +9 -0

Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.

for me there is far to much movement in the UI for this to be of any use
It needs some static elements to be of real use as things stand from the clip shared

Nice. I was a little worried that this would impact the performance, but I tested it with a lot of small files (2.4GB, spread across 8613 files) and the performance stayed the same (around 8.8 seconds). Robocopy is still faster at around 6.1 seconds but that's hard to compete with.

The initial copy found a bunch of hash files in the "hidden" .git folder, so that's the hex numbers you see at the start. However, under normal circumstances if copying lots of folders or larger files, then the content won't jump around so much.

It seems to me that such things are not useful in the sense that they do not solve the problems that they should.
If you have to constantly copy files, then after the first admiration comes the annoyance of useless flickering on the screen.
Does anyone really have time to read and remember file names in this progress bar? Really helps you? Really?

The main thing the progress bar is for is the frozen screen. When a user gets worried that the process is frozen? Usually it is 5-15 seconds. This means that there is no point in displaying the progress bar before this time has elapsed.

The second purpose of the progress bar is to show useful information for the user.
Here we have two things (related to the frozen screen problem).
First, it makes no sense to show file names if you copy many small files. It is enough to show number of copied files (and probably total time/size of copying).
Second, there are situations of long copying of a large file. In this case it makes sense to display the file name and the copying progress to avoid the frozen screen problem - the last does not exist now.

I would like to have an API that allows to do such things OOB and save (module) developers (see for ex., ADUC or EMS (Exchange Server)) from duplication.

Let me try a different approach as a separate PR to see if the perf isn't significantly impacted

See if #18735 is preferred although there is a bigger perf penalty

Closing this in favor of the other one