Paul O'Neill

What version of `tslint` are you using? Also what version of the plugin?

What version of the plugin and tslint are you using? The -f flag hasn't been supplied to `tslint` for a good while now, so just upgrading the plugin might help.

So - and I can't believe I didn't reply to this for so long so I do apologise: - tslint.json should be sought by default now, if you don't specify...

The warning indicates tslint wasnt found in the specific folder you supplied, which needs to be specified relative to the sonar-project.properties file (or the analysis working directory if it has...

The above log suggests that you've configured the sonar-project.properties correctly, but that there's no file at node_modules/tslint/bin. Note - the plugin doesn't ship with a version of `tslint` nor really...

In case this helps anyone else, in my case for some reason the `JsonSerializerDataContractResolver` that was getting used by Swashbuckle to generate the swagger.json file was defaulting to a brand...

Do you have a quick test-case class and expected output I can unit test against? Or is it actually raising an error? To be sure, I've not used New Relic...

That's how New Relic's custom profiler used to require generics be specified - it's a mad combination of the backtick notation you sometimes see in reflection (like List`1) and standard...

From a support ticket I opened in Jan 2013(!) about how to instrument methods with generic parameters:  

Sounds like they've changed how that gets specified then, as once upon a time it definitely worked. As a quick test, try removing the whole parameters attribute from the match...