Choose naming strategy for "Fill with Mock" feature

[OptimumDev]

Hi! Is it possible to make some sort of setting, so you could choose what naming startegy will be used for mock fields created by "Fill with Mock" feature? Currently it creates private Mock<Test> test;, but we are using private Mock<Test> testMock; naming in my team. Because of that, I have to rename each field after creating, which is not very convenient.

[lconstan]

Currently, the naming for fields is chosen depending on the configured naming settings in Rider/R# (see here).

What you'd like is a naming strategy for the fields of type Mock<T>.

How do you currently enforce this naming in your team?
Could the use of an editorConfig file solve your issue?

[OptimumDev]

What you'd like is a naming strategy for the fields of type Mock

Exactly

---

How do you currently enforce this naming in your team?

It's just verbal agreement, we check it during code review

---

Could the use of an editorConfig file solve your issue?

As far as I know, editorConfig doesn't allow you setup special rules for specific type (especially for generics), am I wrong?
I thought that may be you can do some sort of plugin's menu in Rider settings or config file, where users could choose naming strategy

[lconstan]

It may not be quick to implement and should be an opt in to override the naming strategy defined above (default should be the configured naming settings). One may have a look when time allows.
In the meantime, PR are welcome 🙂