fix: change mediaId optional chaining and list response message text obtain #1240
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
|
Fiz mais um commit alterando também em caso de s3 enable
|
|
Temos problemas de lint na sua Pull Request, ajuste isso para que possa ser aprovado sugiro o comando |
|
@DavidsonGomes fiz o ajuste, obrigado por pontuar |
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.
Essa falha para obter o .id causa a sessão em entrar no modo
awaitUser: false, com isso, as interações acabam não chegando mais no typebot (e possivelmente em outros lugares que possuem essa mesma lógica)Fiz o ajuste de optional chaining na hora de obter o mediaId, para evitar esse erro, e ajustei também o modo como o listResponseMessage é acesso (provavelmente alguma diferença relacionada a versão do baileys)