paulirwin commented on PR #13: URL: https://github.com/apache/lucenenet-codeanalysis-dev/pull/13#issuecomment-3415436852
As long as the message of the diagnostic is the same, and the code fix if applicable, you can have as much logic in the diagnostic (and code fix) as you want. So it's fine to have an analyzer that handles lots of different sub-cases. Note though that we do not want to update the Unshipped file with analyzers that do not exist yet. The only thing needed to do to reserve an ID is to update the ranges file at this time. Typically you will update the Unshipped file with the analyzers that are included with your PR. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
