remember the new fragment tile selection #226
Open
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.
Signed-off-by: Balaji Yaswanth Vankala [email protected]
Related Tickets & Documents
What type of PR is this? (check all that apply)
Scope
This PR enhances the user experience by remembering the fragment tile selection and auto-selecting the most used fragment type by default.
Implementation
After a fragment is submitted then the frequency will be stored in the localstorage inside an object
fragmentSelectionCount
via global state context. The state of thedefaultSelected
fragment radio tile will be fetched from the localstorage every time. Out of all, the one with max count will be assigned to thedefaultSelected
.For this feature the auto-selected value will be one of the following:-
Screenshots/Recordings/Diagrams:
How to test
We can verify the fragment selection with the
fragmentSelectionCount
object in localstorage from browser console.[optional] To-do before merge
[optional] To-do after merge