[Archeo] A lógica de roteamento deve ser estruturada de forma que cada tipo de nó (static/param/any) seja tratado em uma função dedicada, com fluxo de controle claro e sem goto statements. - #3090
Draft
GabrielMella wants to merge 1 commit into
Conversation
…po de nó (static/param/any) seja tratado em uma função dedicada, com fluxo de controle claro e sem goto statements.
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.
Correção autônoma para a issue #10802.
A função Route() contém lógica de roteamento complexa com múltiplos blocos de decisão (static/param/any) e backtracking implementado via goto statements (linhas 976, 1069, 1071). A lógica de busca em árvore é dividida em três blocos separados (linhas 960-984, 1017-1037, 1039-1062) com fluxo de controle não-linear que dificulta compreensão e manutenção.