fix: resolve TS2304 build error - undefined maxRetries in whatsapp.baileys.service.ts#3
Merged
Merged
Conversation
…error Agent-Logs-Url: https://github.com/johanpedroo/evolution-api/sessions/ee80d2e4-605d-49a9-95d2-94a19eb03ab6 Co-authored-by: johanpedroo <5067128+johanpedroo@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Fix error TS2304 by adding maxRetries variable
fix: resolve TS2304 build error - undefined Apr 28, 2026
maxRetries in whatsapp.baileys.service.ts
Copilot stopped work on behalf of
johanpedroo due to an error
April 28, 2026 23:11
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.
📋 Description
Docker image build was failing with
error TS2304: Cannot find name 'maxRetries'atwhatsapp.baileys.service.ts:1829. The variable was referenced in a log message inside themessages.updatehandler but never declared in scope.Fix: Replace the undefined
${maxRetries}interpolation with the literal3in the log message — no retry logic exists at that callsite; the value was purely informational in the log string.🔗 Related Issue
🧪 Type of Change
🧪 Testing
📸 Screenshots (if applicable)
✅ Checklist
📝 Additional Notes
Only the log message string is changed. No runtime behavior, retry logic, or control flow is affected.
Original prompt
This pull request was created from Copilot chat.