Goal: Debug console used to show detailed information, such as additional scope, environment, line number of the error, and a trace of which functions triggered as a result of a query run. Was this feature removed or changed?
Details: This used to be visible, no longer visible in some apps.
Should looks something like this:
Hey there @alinomon,
I think the detailed information has always been a part of queries, where as linting errors like the one in your first screenshot have, as far as I can recall, always looked the same.
Hey @MiguelOrtiz I think @alinomon is correct. I also experience the error but found a work around.
Running the same app in user mode and opening the debug modal does show detailed information whereas opening the app in editor mode does not show any dependencies or what environment the script is triggered from. Please see the screenshots:
The app in editor mode:
The same app in user mode:
Please let me know if you can enable this. Seems like a bug!
Hi Miguel,
Thanks for your reply. If you see the attached images, while in user view, expanded information is shown such as additional scope, functions triggered, and environment. However in the developer view screenshot, all of this information is gone. As a developer, I'd like to see the information in the user view debug console, and this used to be the case.
Thanks for your help.
Alex
I am also facing this exact issue: queries showing details in the console in user mode but not in editor mode. Hope this can be looked at because its very inconvenient for me and even leaking data to our app users!
Hello everyone,
Thank you for sharing the screen shots and feedback!
I can file a feature request to have things switched so that editor mode has additional details.
@zas The app should not be providing any data to users that are not within a privilege group that would allow them to see this data.
I believe I had another user bring up a similar point but they root was they were allowing all of their 'end users' to be in a default group with higher than they knew privileges and we filed a bug report to limit this default group!
Regardless, it doesn't make sense for the editor in user mode to be sharing much data anyway since developing and bug testing should be done in editor mode so I can look to have the current debug panels swapped so that if end users encounter a bug they can better report.
But there won't be any critical data like passwords or connections strings as those are always obfuscated to end users.
It feels unclear to me what your saying here. Is this a bug or a feature request? If your request becomes granted, are end users going to be able to see detailed console information or not? I would also like to question the status of "feature request" labeling this request. We used to have detailed information while editing apps in the console view, then something changed that was not requested of anyone, and now we don't have detailed information in the console view. Isn't this more of a bug report? I'm saying this under the assumption that bugs get fixed faster and the lack of detailed information is constraining my ability to quickly sanity check my data flow within my app editing.
Hey @Shawn_Crocker! I appreciate the clarifying question. 
This does sound like a bug, in the sense that it is likely an unintended side effect of changes made elsewhere in the code base. I've reached out to the relevant teams just to confirm that there haven't been any intentional updates, though, just to be sure!
I can certainly appreciate that not having those detailed logs would hamper app development and will keep this topic updated as I learn more. 
Quick update - we were able to tie the emergence of this issue to the rollout of a particular feature flag. We've toggled off that flag while we investigate further, so you should have your detailed logs back! 
Super! Thanks
