These are chat archives for DotNetAnalyzers/StyleCopAnalyzers

9th
May 2018
Sam Harwell
@sharwell
May 09 03:31
@vweijsters @pdelvo Master branch is locked in preparation for the 1.1.0-beta007 release
Sam Harwell
@sharwell
May 09 04:53
branch is unlocked again
Johan Larsson
@JohanLarsson
May 09 11:45
NU1108 is annoying when referencing the analyzer to check the analyzer source.
Sam Harwell
@sharwell
May 09 11:52
hmm?
Johan Larsson
@JohanLarsson
May 09 11:54
Are you referencing the stylecop.analyzers nuget in this project without any issues?
Sam Harwell
@sharwell
May 09 11:54
haven't noticed any nuget-related issues
Johan Larsson
@JohanLarsson
May 09 11:55
I'll give you a repro soon, hold on
Maybe it is a paket issue.
image.png
Sam Harwell
@sharwell
May 09 12:05
One second
Johan Larsson
@JohanLarsson
May 09 12:06
you don't have to spend any time on it, I'm just removing the analyzer
Johan Larsson
@JohanLarsson
May 09 12:06
just pushed in case you are interested
that looks like it can be a hack around the same issue
Sam Harwell
@sharwell
May 09 12:08
It's a 'won't fix' issue so you may as well adopt the same. It works because you aren't creating a NuGet package from this project (created from the code fixes project instead).
Johan Larsson
@JohanLarsson
May 09 12:10
I saw the won't fix, weird imo
Should not be too rare to want an analyzer that checks the analyzer source
I know four repos where that makes sense
not that four is a big number but the idea of having an analyzer check analyzer code is pretty natural
Johan Larsson
@JohanLarsson
May 09 12:24
Looks like the hack did not work, failed on appveyor.