RSRP-287548: Rename parameters to overloaded methods isn't intuitive

If you have overloaded constructors or methods that don't contain the same parameters in the same order, ReSharper seems to "randomly" pick which parameter in an overload to rename and may not rename any parameters in the overloaded methods at all. I don't like code structured this way, but imagine you have a set of overloaded methods something like this:

public void CreatePost(string strUserName, string strSubject, string strBody)
{
}

public void CreatePost(string strUserName, DateTime dtPostDate, string strSubject, string strBody)
{
}

public void CreatePost(string strUserName, string strSubject, string strBody, DateTime dtPostDate, string strCategory)
{
}

If you rename strUserName to userName, ReSharper appropriately renames strUserName to userName in all three methods.

If you rename strSubject to subject, ReSharper renames strSubject to subject only in the first and third overloads.

If you rename strBody to body, ReSharper renames strBody to body in the first and third overloads and prompts to rename strSubject to subject in the second overload.

I don't know if this is entirely true, but it looks as if ReSharper is picking out the parameters to rename based on the position and data type instead of by name. In other words, the first rename works because strUserName is always the first parameter and is always type string. The second rename doesn't work correctly because the second overload has a DateTime as the second parameter so the types don't match. The third rename works a bit odd because the third parameter is of type string so the types match.

If the fix is too complicated, you might close this as won't fix. The bigger issue in my mind that the parameters aren't in the correct order so it makes the code confusing and overly complex.