> What I would find clear: > > bool => iif(str,str) => str
You're right Tim But in the long term it could be great to share a common output format with the doc as well (to find all relevant info from -dKcnv in the doc, and vice versa) While > bool => iif(str,str) => str and > bool | iif(str,str) => str would not fit properly with existing representation for converters within the doc > iif(str,str): str <= bool and > iif(str,str): bool => str could be good candidates (fetches are already represented using "name(arg) : out"), although dconv would have to be patched anyway for this to work since it does not allow '=' nor '>' or '<' characters after the ':' because of this regexp: https://github.com/cbonte/haproxy-dconv/blame/4decf0b72eff0888195c2353ea149cd969110fe5/parser/keyword.py#L31
