▲ | __MatrixMan__ 6 days ago | ||||||||||||||||
I've not heard of tattoy but I'm glad I ran across it. Most of its usage is not to my taste, but it appears to scratch an itch I've had for some time. I've been chewing on this idea for a... terminal emulator? shell? editor plugin?... something where you could annotate an error message with something like: > This is fixed in the next release, nothing to see here or > I think think one is actually a problem, see issue 1657 And then your coworkers could view the logs in some way (special terminal emulator? piped through some kind of filter? idk) and your annotations would appear in a column next to the logs, perhaps with some background coloring to indicate which annotation goes with which log message. This way you don't all duplicate the effort of deciding whether this particular error is worth worrying about--instead you'd leave notes right there on the error (anchored via context triggered piecewise hashes). The tattoy protocol seems like it be a good way to apply the highlighting on the logs whenever one that has a matching annotation appears on screen (https://tattoy.sh/docs/plugins/). | |||||||||||||||||
▲ | DiggyJohnson 6 days ago | parent | next [-] | ||||||||||||||||
That would actually be cool. We have a couple issue patterns with the interface between front and backend that leads to our frontend guys always misinterpreting the reason their API call are failing. Wound be cool to annotate “this error message is usually caused by another error message in <this controller>. Please check for this before assuming…” | |||||||||||||||||
| |||||||||||||||||
▲ | tombh 6 days ago | parent | prev [-] | ||||||||||||||||
This is exactly the kind of creative thinking I want Tattoy to both inspire and make easy to implement. |