If you define a CFC argument as being required="false", and then do not pass it in, it will, of course, return false if you do isDefined("foo") or isDefined("arguments.foo"). However, if you cfdump the arguments scope, you can clearly see foo (or whatever the name of your argument was) in the structure. The value is "[undefined struct value]", which to mean smells like null, but CF has no real support null.
(This post is more than 2 years old.)
Interesting Behavior with Arguments
Support this Content!
If you like this content, please consider supporting me. You can become a Patron, visit my Amazon wishlist, or buy me a coffee! Any support helps!
Want to get a copy of every new post? Use the form below to sign up for my newsletter.