Every time I forget to change an arguments direction when I actually use the naming convention correctly my soul dies a little more…could we add a feature where if you use in_ out_ io_ the direction changes to match the name when you create a new argument
Or just drop the in_, out_ or io_ argument naming convention…?
Its so rarely situationally useful, and, as demonstrated by your issue, cannot even be relied upon then.
Its just ugly visual noise mostly. Free yourself and embrace C# naming styles.
Variables in lowercase, Arguments with the first letter uppercase. Direction doesnt matter.
Hi @DMar,
I agree with you this seems like an easy feature to put in. The naming convention makes sense when looking at the logs so I would not do away with the convention and this suggestion would make a nice ease of use in Studio. I would even take it further and recommend we implement something similar on variables where strFirstName would create a string variable and intAge → Integer. Maybe this could be an extension for those who would want it? 
I’d definitely stick with a consistent naming convention for arguments. Something simple like in_, out_, and io_ makes workflows much easier to understand, especially when someone else has to maintain them later.
I tend to prefix variables/arguments with the data type, and use the lowercase for variables/global variables, upper case for Arguments. It makes it easy to see what data type something is, e.g.
string
strMyVarName
integer
IntTimeoutMS
secure string
sstrPassword
array
arrMyArrayName
I think I find the datatype prefix even more annoying and distracting because at least with the arguments there are 3 defined options and then they are done.
For example common types
LocalResource
ExtendedDocumentData
QueueItem
What should the prefixes be? How about an Array of Bytes? a List of string?
Ienumerable
It starts to get pointlessly complex and obtuse what the short code for the variable means and only really works with the primitives.
I question what value this gives you? If I am in the data manager I can immediately see the data type.
If I am writing code I can see the data type using intellisense instantly and not rely on the name being correct as its sometimes not.
Perhaps I miss a use case you guys have, but where does this help you vs just naming them in a simpler convention such as a the C# type?