paulirwin commented on issue #1188: URL: https://github.com/apache/lucenenet/issues/1188#issuecomment-3368542124
We have a separate repo for our dev analyzers, located here: https://github.com/apache/lucenenet-codeanalysis-dev That is where you will want to fork and PR. We have started on some documentation on how to contribute new analyzers, please review the documentation and let us know if you have any questions. Make sure both your analyzer and code fix have good unit test coverage, based on the existing test structure and patterns. I have reserved ID LuceneDev1006 for this ticket, so please use that. As noted in the original issue text, you will want to base your analyzer/code fix on LuceneDev1001. If you see opportunities to refactor the code to share logic between them and prevent duplication, please do! And thanks again for volunteering to fix this issue! -- 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]
