Skip to content

Conversation

@Zelys-DFKH
Copy link

  • All tests pass
  • I have run npm run doc

Description

This PR consolidates bug fixes and code quality improvements:

Bug Fixes:

  • Fix incorrect API method in unpinAllGeneralForumTopicMessages (was incorrectly calling unhideGeneralForumTopic)
  • Fix incorrect API method in replaceStickerInSet (was incorrectly calling deleteStickerFromSet)
  • Fix memory leak in reply listeners by properly removing listeners after callback is invoked
  • Fix typo in variable name businesssMessagebusinessMessage
  • Use safer Object.prototype.hasOwnProperty.call() pattern instead of direct hasOwnProperty

Compatibility:

  • Pin tough-cookie to ~2.5.0 for Node.js 8 compatibility

Documentation:

  • Fix spelling: "miliseconds" → "milliseconds"
  • Fix spelling: "occured" → "occurred"

References

claude and others added 5 commits January 2, 2026 16:59
The tough-cookie v5.x dependency pulled by @cypress/request uses
optional chaining syntax (?.) which is not supported in Node.js 8.
This was causing a SyntaxError during test execution.

Pin tough-cookie to v2.5.0 which is compatible with Node.js 8.
…TvP9z

Fix Node.js 8 compatibility by pinning tough-cookie version
This commit addresses several issues in the codebase:

- Fix unpinAllGeneralForumTopicMessages calling wrong API method
  Previously called 'unhideGeneralForumTopic', now correctly calls
  'unpinAllGeneralForumTopicMessages'

- Fix replaceStickerInSet calling wrong API method
  Previously called 'deleteStickerFromSet', now correctly calls
  'replaceStickerInSet'

- Fix memory leak in reply listeners
  Reply listeners are now automatically removed after being triggered,
  preventing unbounded memory growth in long-running bots

- Use safe hasOwnProperty check
  Replace direct obj.hasOwnProperty() with Object.prototype.hasOwnProperty.call()
  to avoid issues with objects that may not have this method

- Fix variable name typo
  Rename 'businesssMessage' to 'businessMessage' for consistency

- Fix spelling errors in comments
  Correct 'miliseconds' to 'milliseconds' and 'occured' to 'occurred'
…ons-LM946

Fix critical bugs and improve code quality
Reflects spelling corrections from source files.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants