feat: add Go and Java support to universal complexity parser - #3
Merged
Conversation
Owner
|
Desculpe a demora para o merge, eu tinha várias mudanças que eu não tinha commitado ainda, então tive que alterar o teu PR e fazer um Co Commit com as novas funções. Obrigado por contribuir!!! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
📝 Descrição
Adiciona suporte a Go e Java ao analisador de complexidade do BigON. Foram criados
GoUniversalParsereJavaUniversalParser(src/analyzer/universal/parsers/), seguindo o mesmo padrão heurístico já usado para C++ (linguagens baseadas em chaves{}): detecção de funções, extração de laços (passo linear vs. logarítmico) e detecção de chamadas recursivas. Os novos parsers foram registrados noUniversalParserRoutere nosactivationEventsdopackage.json(onLanguage:go,onLanguage:java).Também corrige um bug de roteamento no
ComplexityEngine.analyzeCode: o caminho para o parser universal só verificavapython|ruby|cpp|c, entãogo/javacaíam silenciosamente no analisador AST de TS/JS e retornavam zero funções.README.md e CHANGELOG.md foram atualizados para refletir as novas linguagens suportadas.
🔗 Issue Relacionada
Closes #1