s992 / chromelogger-cf Goto Github PK

Chrome Logger has support for console.table(). See https://craig.is/writing/chrome-logger/techspecs and https://github.com/ccampbell/chromelogger/blob/6a618e313bb26c9b41b3723e1b3ea7cd0ec611cc/log.js#L29.

So support for it should also be added to chromelogger-cf to allow the generation of data tables.

This could then also be used to output query results in a nice way.

Sebastian

Hi,

The original Chrome Logger extension isn't being updated - the maintainer ignore pull-requests and has been unresponsive on all channels.

I'm not sure if you're still maintaining this library? But I've published an alternative Chrome extension that adds a dedicated "Server Log" panel.

Would you please consider adding a link?

You also might consider adding support for the X-ServerLog-Location header, which enables you to break the header-size limitations (in Chrome, Apache, NGINX, etc.) and remove the cap on log size.

Thanks,
Rasmus

I am using CF9 and am getting an error.

Maybe I am not instantiating the component correct? Please advise.

Chrome Logger has support for console.table(). See #8 for more info on that. This allows to display tabular data.

And since query results are tabular data, it would be great if they were displayed as such.

I can also imagine the query string and the meta data to be logged like it happens when dumping a query.

Sebastian

I've just tested chromelogger-cf with Lucee 5.3.7 and the Chrome Logger extension in Firefox 86 (Nightly) and it works. See the attached screenshot:

So this note can be added to the README.md.

Sebastian

The generation of the backtrace information doesn't work in Lucee 5.3.

The reason for that is that the stack frames returned by createObject( "java", "java.lang.Thread" ).currentThread().getStackTrace() provide relative paths, while getMetaData( this ).path contains an absolute one.

Sebastian