In the debugging template we are missing "debugging.implicitAccess".
Even if the checkbox (in admin debugging) is active, this argument doesn't exist anymore.
Or was the logic changed and it will only exist if some variables are not scoped correctly?
i’m sorry for the inconvenience, that was by design not by accident.
pointed to the right commit, we made “pages“ optional so you can have a light version of the debugging that only shows you the basic stuff, you may also can use in production. As part of make it lighter, we also removed all unnecessary steps and data. including to create a query object that is not needed because it is empty. as you can see in the commit we had to rewrite the debugging templates coming with Lucee, but we did not consider 3 party to relay on the debug data.
i will change it, so you get it in case the flag is set, even there are no records. BUT that will still break your code in case it is not enabled. What do you think?
I think the changes you did make sense, I am am always in favor of changes which improve the performance. This is not a big issue for us. We already changed our debug template and it works, so we would not need the flag. I understand the reason for these changes now, so imho you could close the issue.
I’m happy you get my point,but i did still change it for others that maybe in the same situation you are.
You now always get the object when the flag is set, independently of it has records or not, so only if the flag is not set, you don’t get it. That has no negative impact on performance for someone not interested in that info. i think that is a good compromise. Thanks for the input.
I've checked this ticket with fixed version 220.127.116.11-SNAPSHOT. Yes, the issue was fixed in the fixed version.
Now ImplicitAccess is available in debugging logs if there is no records available.
Could you please check with fixed version and report here back.