[codex] fix emission signature placement#6
Merged
Conversation
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
1 participant
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.
Summary
InfDeclaracaoPrestacaoServicobut emit<Signature>as the next sibling inside the enclosing<Rps>containerRoot cause
Homologation rejected
GerarNfsebecause the emitted XML placed<Signature>inside<InfDeclaracaoPrestacaoServico>. The current municipal schema expects the emission signature at the declaration container level, afterInfDeclaracaoPrestacaoServico.Validation
go test ./internal/xmlsig ./internal/servicego test ./...go test ./... -race -coverprofile=coverage.outgo vet ./...go mod tidy && git diff --exit-code go.mod go.sumgo run ./cmd/nfe emit mova --wait-timeout 90ssucceeded for RPS 36