You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 16, 2022. It is now read-only.
In the list of linked options on the sidebar, for logged in users, "Example Sets" should link to the appropriate heading.
If on the main dashboard showing all sets, this should scroll the page (no refresh needed) so the "Example Sets" heading is at the top of the page.
If on another page besides the main dashboard, this should bring the user to the main dashboard, and scroll to the "Example Sets" heading.
If the user is in the middle of editing something (e.g. editing a problem, editing a problem set), this should save any edits which have been made prior to bringing the user to the main dashboard and the "Example Sets" heading.
Acceptance criteria:
Given that I'm a user on a screen wide enough to view the sidebar, I should encounter the "Example Sets" link underneath either My Sets, or My Solution Sets & My Created Sets. When I click the "Example Sets" link, any edits I've made should be saved (if applicable), and I should be brought to the appropriate heading on the dashboard.
The text was updated successfully, but these errors were encountered:
This issue was coming due to the api taking more time and the scroll hapenning before the data was loaded which was pushing the content down.
I have added a wait for the data to be completely loaded before the scroll happens
In the list of linked options on the sidebar, for logged in users, "Example Sets" should link to the appropriate heading.
Acceptance criteria:
Given that I'm a user on a screen wide enough to view the sidebar, I should encounter the "Example Sets" link underneath either My Sets, or My Solution Sets & My Created Sets. When I click the "Example Sets" link, any edits I've made should be saved (if applicable), and I should be brought to the appropriate heading on the dashboard.
The text was updated successfully, but these errors were encountered: