SerializeJSON with a query object in argument 1 and a boolean "1" in argument two returns
invalid call of the function SerializeJSON, second Argument (options) is invalid, When var is a Query, argument [options] must be either a boolean value or a string with the value of [struct], [row], or [column]
Same code worked fine in 184.108.40.206. Seems to work in our test environment under 220.127.116.11-SNAPSHOT as well.
IIS10 Win Server 2016
that happens when we add addional arguments when implement a function ACF has. then later ACF adds addional arguments as well.
I totally understand . If we could just allow for boolean arguments in the 2nd and third arguments (which would translate in to options? ), it would really help. Right now, I have to do this in one of one of our Coldbox modules to support both engines:
Not having to do engine detection, would make it easer to migrate ACF apps to Lucee too!
I’m working on this ticket and hopefully will resolve it soon (or come back with more questions).
we still miss the attribute “useCustomSerializer“ all the other attributes now are acf compatible and backward compatible.