I am currently needing to reverse-engineer the messages in the JSON file in order to display coordinates given by outline check results in my font editor. This is a tedious process involving regex (as well as different expressions for every check, since the formats are often slightly different).
Expected behaviour
It would be immensely useful to have a more accessible form of output. For example, in the "message" dictionary, in addition to the "message" and "code" dictionary, something like a "glyphs" dictionary with "name" and "coordinates" keys would be very accessible.
That way, when processing a fontbakery JSON file, one could simply access the affected glyphs from a check, as well as the coordinates in question.
I realise this is only useful for outline checks, but since these constitute the most laborious part of checking, an improvement in how outside applications can process (and visualise) this code would be fantastic.
Observed behaviour
I am currently needing to reverse-engineer the messages in the JSON file in order to display coordinates given by outline check results in my font editor. This is a tedious process involving regex (as well as different expressions for every check, since the formats are often slightly different).
Expected behaviour
It would be immensely useful to have a more accessible form of output. For example, in the "message" dictionary, in addition to the "message" and "code" dictionary, something like a "glyphs" dictionary with "name" and "coordinates" keys would be very accessible.
That way, when processing a fontbakery JSON file, one could simply access the affected glyphs from a check, as well as the coordinates in question.
I realise this is only useful for outline checks, but since these constitute the most laborious part of checking, an improvement in how outside applications can process (and visualise) this code would be fantastic.
Thank you for considering!