Long bundle path causes truncation of text in GitHub UI about bundlesize

[siddharthkp]

Sounds good!

[palashmon]

I am not working on this case yet, but I just wanted to discuss some test case scenarios and gets inputs from other also. This might be helpful for any other contributor who wants to work on it in future.

• Best case scenario

  When file name is short like:

  ./dist.js
  

  In this case no truncation of text is needed.

• 2nd scenario

  When file path is long like:

  ./lighthouse-extension/dist/scripts/lighthouse-background.js
  

  In this case, I think we can truncate it to like ~/lighthouse-background.js.
  What do you think?

• 3rd scenario

  When file name is long (more than 35 chars) like:

  ./lighthouse-background-long-filename.js
  

  In this case, I think we can truncate it to something like ~/light...name.js.
  What do you think?

What other test case scenarios we have?

[siddharthkp]

I like all of those solutions!

I'd also like to add the case of multiple files in possibly different folders.

[siddharthkp]

Another thing I'll throw into the mix is: should we do this in the CLI or on the store/details page.

Doing it in the CLI is a more effective use of URL length, but doing on the details page gives us the flexibility of deploying whenever we want even with breaking changes.

[siddharthkp]

Whoops, we should this conversation to #81

[vs1682]

You mean showing the path with it's parent directory, right?
Like
~/parent1/file1.js
~/parent2/file2.js

[siddharthkp]

@vs1682 yep.

moved to #82