Remove Audio Scroll Settings from SG Settings page. #365
Merged
Conversation
- Removed unused audio sync scroll functionality and related state management for a cleaner codebase. - Updated audio settings configuration to streamline the audio options presented to users, focusing on audio and auto-play features.
Gauravjeetsingh
approved these changes
Dec 22, 2025
smanjot27
pushed a commit
to manjotkaur27/sundar-gutka-react
that referenced
this pull request
Mar 28, 2026
- Removed unused audio sync scroll functionality and related state management for a cleaner codebase. - Updated audio settings configuration to streamline the audio options presented to users, focusing on audio and auto-play features.
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
2 participants
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.
The Audio Scroll Settings have been removed from the SG Settings page for now. We will implement this in future. I have created seperate issue. #362