Certificado digital em memória#40
Open
jalesc wants to merge 1 commit intonfse-nacional:mainfrom
Open
Conversation
a21ns1g4ts
approved these changes
Apr 30, 2026
|
Codecov Report❌ Patch coverage is
📢 Thoughts on this report? Let us know! |
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.
Antes, para emitir uma NFS-e era obrigatório ter o arquivo .pfx salvo em disco e passar o caminho até ele. Isso funcionava bem em muitos cenários, mas criava dificuldade para quem armazena o certificado em banco de dados ou qualquer outra fonte que não seja o sistema de arquivos do servidor.
Com essa mudança, o NfseContext passa a aceitar também o conteúdo do arquivo diretamente, via certificateContent. Quem já usa certificatePath não precisa mudar nada — tudo continua funcionando exatamente como antes.
Como usar:
Antes (continua funcionando)
Novo: passando o conteúdo diretamente