fix: remove maybescroll console debug#1053
Merged
kirillzyusko merged 1 commit intokirillzyusko:mainfrom Jul 28, 2025
Merged
Conversation
Owner
|
Ooops 🙈 Thank you for opening the PR! ❤️ I approved, when CI pass I will merge it! Thank you again for the contribution! |
Contributor
📊 Package size report
|
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
Removed a redundant console.debug statement from the library that was unnecessarily polluting the logs. This is the only one in the code so I suppose it was a development log that has not been deleted.
💡 Motivation and Context
No functional or behavioral changes were made to the codebase. This is purely a logging cleanup.
📢 Changelog
JS
🤔 How Has This Been Tested?
The change was tested manually by running the application and confirming that:
• The noisy debug message no longer appears in the console.
• All existing functionality continues to work as expected.
• No errors or regressions were introduced.
Unit tests were not affected as this change does not alter any logic or data flow.
📸 Screenshots (if appropriate):
📝 Checklist