Closed isc-tleavitt closed 9 months ago
On further review, we only export code for things on which we've collected coverage data. Solution in this case: don't collect coverage data on stuff from ENSLIB. (And if you do, you want/need the source exported.)
There might have been some different context here, but I think all is working as intended at this point. Not an ongoing issue we're seeing in my team's use cases.
For reporting (e.g., cobertura) we shouldn't export mapped classes - this can pick up things from ENSLIB and therefore does needless work.