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
I'm publishing HTML coverage reports generated by istanbul with the help of workarounds shared in #3027. The result is styled correctly, but there is a problem with unicode characters both in FF and Chrome:
The symbol is display correctly locally, but not after I upload the HTMLs to VSTS. The reason is because VSTS strips <meta /> html tags from the HTMLs including <meta charset="utf-8" />.
What would recommend to do to overcome this limitation? Character × is not the only non-ASCII symbol that the coverage reports can contain. Other examples include emojis in code as well as comments in Chinese or Cyrillic.
The text was updated successfully, but these errors were encountered:
@kachkaev Thanks for reporting this. Currently we are revamping the code coverage experience and no plans to enhance current experience.
Closing this issue and we assure that this experience will be improved sooner.
Thanks for your reply @nigurr! What link would you recommend me to track not to miss the update? What’s the approx order of the ETA (days, weeks, months)?
@kachkaev Please follow Azure DevOps Release Notes, we update the rollout in the notes. Currently we can't share the exact timelines, however the work is in progress.
Task: Publish Code Coverage Results (v 1.*)
I'm publishing HTML coverage reports generated by istanbul with the help of workarounds shared in #3027. The result is styled correctly, but there is a problem with unicode characters both in FF and Chrome:
These are supposed to be
3×
,2×
and1×
(× being a utf8 multiplication sign).The symbol is display correctly locally, but not after I upload the HTMLs to VSTS. The reason is because VSTS strips
<meta />
html tags from the HTMLs including<meta charset="utf-8" />
.What would recommend to do to overcome this limitation? Character
×
is not the only non-ASCII symbol that the coverage reports can contain. Other examples include emojis in code as well as comments in Chinese or Cyrillic.The text was updated successfully, but these errors were encountered: