You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Viewing Gramex logs in the browser is very important for the IDE (not sure if this is also true for UAT). So switch to rich (or anything else) as long as it provides easy configuration of logging to HTML as well as the terminal.
What I mean is - I don't want to write too much code to render Gramex logs on web pages. Maybe something like this:
gramexlog:
color: ascii # orcolor: html # And then simply pipe the STD{OUT, ERR} to an html file
________________________________
From: Jaidev Deshpande ***@***.***>
Sent: Saturday, November 5, 2022 4:09:36 PM
To: gramener/gramex ***@***.***>
Cc: Sandeep Bhat ***@***.***>; Mention ***@***.***>
Subject: Re: [gramener/gramex] Switch to rich for logging in color (Issue #634)
Viewing Gramex logs in the browser is very important for the IDE (not sure if this is also true for UAT). So switch to rich (or anything else) as long as it provides easy configuration of logging to HTML as well as the terminal.
—
Reply to this email directly, view it on GitHub<#634 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AQC65A6M2YVYOOWFFLENVNDWGY2ORANCNFSM6AAAAAARW27WNA>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
Disclaimer: This email may be confidential. Please don't share without consent. Inform the sender if you got it by mistake.
rich has a good interface for logging in color. Should we switch to this, @bhatsandeep @jaidevd?
The text was updated successfully, but these errors were encountered: