[ Fix : Snackbar Component Placement, Uses and State Management ] #1141
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
In this pull request, I addressed the issue where Snackbar components were not displaying or activating properly. I observed that the Snackbar components were placed within functions, onClicks, or other locations without proper state management. To resolve this, I moved the Snackbar components to the appropriate places and implemented proper state management. My Code Changes reflected in 'StepTitle' 'RemoveStepModal' 'ControlButtons'
Related Issue
Fixes #1118
Motivation and Context
To utilize the Snackbar component correctly and ensure consistent behavior.
How Has This Been Tested?
I tested these changes locally on my machine, focusing on scenarios where Snackbar components were used.
Videos demonstrating at places they are changes by me :
In Step Title:
Codelabz.-.Google.Chrome.2024-01-24.15-58-56.mp4
In Remove Step Modal:
Codelabz.-.Google.Chrome.2024-01-24.15-39-57.mp4
In ControlButtons:
Codelabz.-.Google.Chrome.2024-01-24.15-15-28.mp4
Types of changes
Checklist: