[FIX] Tratamento do XML de resposta #59
Merged
Conversation
This file contains 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
2 tasks
felipezago
force-pushed
the
fix/xml_resposta
branch
from
4098108 to
2d96f80
Compare
rvalyi
approved these changes
Jul 16, 2023
mileo
approved these changes
Jul 19, 2023
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.
Foi necessário alterar a forma de tratamento do XML de resposta, devido ao fato de alguns serviços da sefaz retornarem o XML com mais de uma tag, como é o caso do
retDistDFeInt:Nesse caso o tratamento era feito na primeira tag encontrada,
nfeDistDFeInteresseResultao invés da tag corretaretDistDFeInt, fazendo com que a classe responsável pelo tratamento não encontre os dados para processar.Para resolver, busquei por tags com o nome igual ao nome da classe responsável pelo tratamento, e caso não encontre nenhuma classe com esse nome, somente então utiliza a primeira tag encontrada.