I’ve never used setter injection, but it sure seems odd that the argument used to be named “s”.
I would guess that used to be an errant behavior that has been fixed.
~Brad
Doesnt really matter that its called s or fred for that matter. Its
inside a method and people using it should care what its called.
So i now have to change all my cfcs that i have want to use in
wirebox?
What about if i want to use this with a third party cfc? I have to
start changing thier code? And if its a java class inside a jar, does
this still apply?
Bit of poke in the eye for encapusulation no?
Why the change from the previous version of wirebox?
Is there a work around for cases where you dont want to/cant change?
Here is the snippet of code from the coldbox coldfusionn best
practices for setters. The argument is not called firstName.
// Property name is firstname
<cffunction name="setFirstName" output="false" access="public"
returnType="void">
<cfargument name="value" type="string">
<cfset instance.firstName = arguments.value>
</cffunction>