Thank you @mhils for your reply.
Great! Definite +1 from me for adding this to the public API.
It’s a bit strange that it prints
str() — I wonder what use cases you had in mind? But of course it’s trivial to wrap my string in a custom class that returns self from
__repr__, so not a problem.
Just to be clear, the string that I want to put there is a few lines worth of text, maybe a few short paragraphs.
mitmweb doesn’t show this metadata though, but that must be easy to fix.
All I need is a way to distinguish flows that have (my) metadata from flows that don’t.
flow.icons sounds great — I would then mark some flows with the letter ‘E’, others with the letter ‘c’, and the rest with no icon at all.
By analogy with
flow.metadata, I think
flow.icons could be a set of (single-character) strings, rather than just one string. That would make it easier to toggle the icons independently, and potentially each icon could be drawn in its own column (across all flows). But of course I can manage a single string as well.
I see. Well, if I had metadata and icons, logging would be a secondary feature at best, so managing the order is not important for me then. Anyway I can add my own indications of which flows I’m referring to.
Thank you, I’ll definitely pop in at some point. mitmproxy is a great tool and I’d love to contribute. The above features (metadata in mitmweb, icons) sound like they could be a good fit for me. But probably not sooner than a couple months, so if you wish to do it yourself, by all means have a go