-
Notifications
You must be signed in to change notification settings - Fork 531
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Color Status Token #107
Color Status Token #107
Conversation
Just an additional default token for colorized status codes. Not sure if it would be wanted or useful.
Thanks! The concept seems fine, just a few issues:
In addition to this, this PR should also DRY up the |
Thanks for the feedback. I will get the details hashed out and resub. |
Cool :) Just update this pull request with the new changes and ping me when they are included and I'll take another look :) |
Depreciate Dev compile fn, and use dev colorize code in colorstatus token.
@dougwilson Dried up the dev compile to the string format. Added test for new token, and corrected test for dev to account for the resulting changes to responses, left in the color test in dev even though they were a little redundant. Added colorstatus token to docs. Also, changed the color code to be more inline with the original implementation from dev. Sorry if there was any build spam. |
README.md
Outdated
@@ -159,6 +159,10 @@ If the request/response cycle completes before a response was sent to the | |||
client (for example, the TCP socket closed prematurely by a client aborting | |||
the request), then the status will be empty (displayed as `"-"` in the log). | |||
|
|||
##### :colorstatus | |||
|
|||
The colorized :status of the response. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please add documentation about which statuses get which colors.
…o dev via token. Revert dev test changes. Not sure if color reset should be documented.
The last comment on this was on May 28. Is this still on track to being implemented @frankydp? Seems like a revert of a removed test is still pending. |
@arikalfus Revert was committed, with a clear added to accommodate, back on May 28th. Pull seems to have conflicts now though. |
Hi @frankydp , sorry, until very recently GitHub did not send any notice when PRs where updated, so since your last update you never posted a comment, I didn't realize you pushed anything else, very sorry for the misunderstanding! Looking over the PR, there are still a few issues to be resolved:
|
Closing the PR since I never heard back and there are conflicts that prevent merging. |
Just an additional default token for colorized status codes. Not sure if it would be wanted or useful.