What do you think of this behaviour: <https://tryc...
# cfml-general
a
It makes sense I guess (or does it?) because the
name
attribute value is a string, not an expression. So perhaps I ought not expect the safe-nav operator to work there.
b
If I'm understanding, I would call it expected since the name attribute is not accepting an evaluate-able CFML expressions, but just a string that contains the variable name. That said, I'm not sure how that name is actually being used internally as the error is worded a bit weird
a
Yeah, you're understanding it right. The error had lead me to believe it was trying to "do something" (
evaluate
?) with the passed-in string, and messing it up. Instead of... what should it do... reject it cos it'd a completely invalid variable name, and that's what it should treat that string as?
b
Yeah, an error telling you your variable name was invalid would have made more sense
a
The docs say "Name of the parameter (variable) to test". so given it's not one of those, that's what it should tell me is wrong
Lucee has lifted the same text, just punctuated it differently https://docs.lucee.org/reference/tags/param.html