Join GitHub today
Configurable naming conventions #380
Somewhat related: #31
Rubberduck could let users configure naming conventions, and have inspections to enforce them.
I can think of a number of ways to specify a naming convention:
..and a number of identifier types to define the naming conventions against:
So, a naming convention could be defined like:
And then there could be inspections (a new
The settings dialog would need a new page to:
I suggest to bake the following conventions as default:
I'd also make one that recommends encapsulating class module private fields into a private type, and only having one private field in a class, called
I think this is a wonderful idea, but considering that VB6 is case insensitive, I'm skeptical about how well this will work in practice. I'm interested in seeing this happen, but am also glad to see you've already planned on a way to let the user disable it.
referenced this issue
Feb 3, 2017
I would like to ask you to review/participate my idea regarding namings and if it maybe would be possible, to add those (or similar) rules, maybe configureable, to RD:
@UnhandledCoder Stack Overflow isn't a good place for that discussion, which is inherently opinionated.
In fact, there's a reason this issue has been open for so long: I don't believe in (most) prefixes, and IMO if you're reusing a name in a different case than what it was originally used for, then the solution is to find a better name, not to prefix it with some random character.
Seems this feature goes against the spirit of
I absolutely agree. finding good names is the base of all.
In that simple situation we have the problem with the spelling of