Skip to content
This repository has been archived by the owner on May 16, 2023. It is now read-only.

Handling failed post delete service calls #79

Open
wants to merge 67 commits into
base: main
Choose a base branch
from

Conversation

maleekha
Copy link
Contributor

@maleekha maleekha commented Oct 13, 2020

Summary of the changes

  • Adding a synced-state in each store which gets updated only when post/delete calls succeed, and is also shown to the users on the preview page/student view page.
  • In case any post/delete call fails, a sticky message is shown at the top of the page with a pertinent error message based on the service error type. An error is also shown in case the user state is not synced with (even when all the calls succeeded).
  • A spinner on the top of the page to indicate that some service calls are in progress.
  • Warning inside modal when the user tries to publish the assignment and (I) some service calls are in progress, or (II) the assignment is not synced (due to some error or otherwise).
  • Failure message in case publishStatusChange call fails.

nehalilani and others added 23 commits October 9, 2020 01:50
…entLinks

2. StudentView page & preview page will show only AssignmentLinks synced with the server and not those links which were not successfully added to the assignment.
3. Publishing the assignment will show appropriate message if data is not synced
2. removed extra comments
error handling for POST calls in Assignment.store
maleekha and others added 28 commits October 19, 2020 16:22
… items in error state --TODO: use them to store-level error show/hide messages.
making errorMsg to be at store level
adding AssignmentUpdateFailureMessage bar to student view as well
removing unnecessary commented lines
changed learn-content to Microsoft learn content
updated isSynced logic for LinkStore and included serviceCall in progress to determine if a satore has an error or not
tweaked how the assignment gets updated
@leestott leestott requested a review from nehalilani March 4, 2021 16:05
@leestott
Copy link
Contributor

Just waiting/scheduling time with Engineering for regression testing to ensure this does not break any aspects.

No Impact to exiting deployment, so users can deploy the services without this change,

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants