sap:VirtualizedContainerService.HintSize Updates

Help
1

Hello,
When we are updating our workflows, there is always a large number of sap:VirtualizedContainerService.HintSize changes that show in git when we commit. These are nothing intentionally changed, but make peer-reviewing the xaml files very tough. Is there a way to turn these hint size updates off?

5 Likes
2

Hi @sheltbh,

Have you already found a solution or workaround for this? Our team is currently experiencing the same issue. It’s very annoying in terms of readability.

Thank you in advance.

Best regards,
Alan

3

hi @sheltbh and @RPAlan

have you guys found any solution/workaround for this? Currently experiencing this and merging conflicts is getting a tad more tedious

Thanks in advance!

Regards,
Brian

4

What does the hint size refer to in uipath studio?

5

Any solution for this?

6

hi

I am also in trouble
have you guys found any solution/workaround for this?

7

Joining in on this issue. Would love to find out how we can suppress all of the “hint size” changes at every commit.

8

Hello,
It seems to be related to the underlying WWF technology used to generate the XAML behind the workflows. I think that it only describes a non-essential property of each block in the workflow.

9

Hello,

I made a few tests and a bit of research and it seems that:

  • The sap:VirtualizedContainerService.HintSize attributes in the XAML file are not essential to the workflow, but further testing should be carried out; as an initial result, after removing all such attributes from a XAML file, I was able to reopen it in Studio just fine; moreover, when editing the file, some but not all of these attributes were added back by Studio.

  • If the above is true (i.e. that these attributes are not essential to the workflow files) then one could first run a script on all edited files and remove these attributes with a regex like sap:VirtualizedContainerService[.]HintSize="\d+[.]?\d*,\d+[.]?\d*"\s before uploading to git (the regex makes for just one of the patterns the attribute follows, so the approach should be flexible enough to allow additions of other patterns).