Quote from: splittingred at Dec 13, 2010, 08:47 PM
Because that’d be against the standards we’ve set (similar to Snippets), and $fields is improper, since the values passed in may not always be "fields".
They won’t necessarily be script properties either, from the point of view of the caller. I just thought it was confusing since users will most often call them from a snippet and in most cases, they’re not sending along the snippet’s $scriptProperties array. If FormIt or Login end up calling processors, they’re not going to send their $scriptProperties array in the call. Also, the processors don’t have any default properties or property sets associated with them (that I know of), so you’re not sending *their* script properties either.
Maybe there’s something I’m not getting, but to me $scriptProperties makes sense for objects that have properties, such as snippets, but using it elsewhere dilutes the meaning semantically to something like: "any array used by a script."
It’s always better if function argument names make sense on both ends, but if that’s not possible, they shouldn’t be named for something else that you’re already using in a snippet, IMO.