Using Find within Studio and "best practice" around using .NET arguments - difference in (arg1,arg2) vs (arg1, arg2) [note the space]

I found a very subtle aspect of coding for Uipath Activities within Studio and how Find handles “(arg1,arg2)” vs "(arg1, arg2).

For example, when using .NET method “Substring” within activities in multiple xamls, Find treats all these method strings as identical values:

  • substring
  • Substring
  • SubString

It will find them all in the xamls throughout your project where it is used.

However, the Substring argument area is a different matter. “Substring(0,15)” and “Substring(0, 15)” (note the space) are not identical to Find because of the space following the comma. UiPath treats them as different. “,<space>” IMHO helps with readability.

I’m just using Substring as the example. I’m assuming this goes to any .NET method argument area used within Studio.

Is this intentional in how Studio Find works treating (arg1,arg2) and (arg1, arg2) as different when execution wise they both work fine ?

Is using “,<space>” in .NET method arguments area considered a bad practice ?

Hello @riverrat437!

It seems that you have trouble getting an answer to your question in the first 24 hours.
Let us give you a few hints and helpful links.

First, make sure you browsed through our Forum FAQ Beginner’s Guide. It will teach you what should be included in your topic.

You can check out some of our resources directly, see below:

  1. Always search first. It is the best way to quickly find your answer. Check out the image icon for that.
    Clicking the options button will let you set more specific topic search filters, i.e. only the ones with a solution.

  2. Topic that contains most common solutions with example project files can be found here.

  3. Read our official documentation where you can find a lot of information and instructions about each of our products:

  4. Watch the videos on our official YouTube channel for more visual tutorials.

  5. Meet us and our users on our Community Slack and ask your question there.

Hopefully this will let you easily find the solution/information you need. Once you have it, we would be happy if you could share your findings here and mark it as a solution. This will help other users find it in the future.

Thank you for helping us build our UiPath Community!

Cheers from your friendly