IssueTracker

Let's say I have multiple generators, each responsible for one library and I have one sample app for all libraries (e.g. accompanist).

When I run all the generators, I'll get multiple HRF profiles, which I can later copy to proper places.

Could we have an optional argument to name to output HRF file instead of class_testname?

This way I could name it in a way, the pipeline later will know what the filenames would look like and I don't have to carefuly name the class and method to match it.