Hello, concerning the ability to provide filename, it is working perfectly. Just one remark even if I don't know if it could be corrected.
it is very handfull to be able to open a file that is mentionned in a warning. This is possible using the file "field".
sometime instead of the mentionned file (because there are no mentionned file), i put in the file field the name of the file being parser. Here again it is perfect because I'm able to open the parsed file at correct line/column and this is very handfull to have the context of an error (previous error message for instance)
but for some parser I have a file mentionned in a warning and also it could be very handfull to be able to see in the parsed file (or console) when the warning occurs. this could be done with fileName variable. But problem because there is only one "file field" that allow to have a link to a file.
would it be possible to have second "file field" so that we could have "parsed file" + "mentionned file" links ?
or maybe simpler, be able to have category or type field to act as a "file field" :
=> when a file is provided in type/category, include a link to it (correct line)
=> when a file is provided in type/category, display only filename and not the path (I already deal this using groovy script)
=> when a file is provided in type/category with a line, consider that filename:X and filename:Y are the same file and not different kind of categories
Your correction provides already a great advance for parsing simulation of FPGA developpement.
But this last correction would be a nice improvement. don't know if it would break a lot of stuff.