add a debug=no option for the various ways that query parameters can be assigned
that way sensitive data can be prevented from being exposed in debugging query output,
i.e for passwords, tokens etc
After get merged for the fix on LDEV-2344, We can't see any param values. This is the sample output from the modern debugging template,
I think we don't need to add a new attribute "debug" for queryParam.
IMHO that sucks, because now you can’t just grab the query from the debug output and run it in a sql profiler which is really useful, especially when doing performance tuning
I think the proposed debug attribute is a far more developer friendly flexible approach.
Could an option be added to the template config to hide all parameter values from queries?
I think, No need to add that option to show/hide the param values. Because param is mainly used to secure the data. ACF also work in that way. Here is the reference from adobe that describes more about queryparam.
This would also be really useful to exclude large inserts from being cached in the debug logs and memory