"Allow public read" switch: no success toast, and the error toast has no Retry
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- Half a day
- Newbie friendliness
- 74/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- react, typescript
- Domain
- frontend
Research direction
Start in src/library-authoring/components/PublicReadToggle.tsx, in onChangeToggle, where showToast is currently called only in the .catch. Show a success toast once the PATCH to /api/libraries/v2/<lib>/ resolves, and add a Retry action to the error toast built from publicReadToggleDefaultError, using Paragon Toast's action prop. Done when a successful flip shows a confirmation and a failed one offers Retry that resends the same change.
Written by the indexing model from the issue text.
Description
The library sidebar's "Allow public read" switch (src/library-authoring/components/PublicReadToggle.tsx, added in #2942) gives no confirmation when a change succeeds. Flipping it sends PATCH /api/libraries/v2/<lib>/, which answers 200, and the switch moves, but no toast or other message appears.
The acceptance criteria in openedx/openedx-authz#239 ("US: M2.9 Toggle reuse content library") ask for:
- the control disabled with a saving state while saving: done (
disabled={… || isPending}); - a success toast on success: missing.
onChangeToggleonly callsshowToastin the.catch; - on error, an error message with a Retry action: partly done. The error toast (
publicReadToggleDefaultError) has no Retry.
Impact: this switch changes who across the instance can view and reuse the library's content. The person flipping it gets no confirmation that it took, and if it fails they must find the switch again to retry.
Expected: show a success toast after the mutation resolves, and add a Retry action to the error toast (Paragon Toast supports an action), as #239 describes.
Environment: Tutor main, 2026-09-22. Code as on master 2026-10-13. Found by the Open edX end-to-end test suite (BTR TC-00575).
- Dominant language
- TypeScript
- Stars
- 18
- Forks
- 228
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 24
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from openedx/frontend-app-authoring
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
openedx/frontend-app-authoring#3310 ·
Maintainers usually reply within 1 day
-
Library Add Content buttons and preview-changes actions are identifiable only by label or positionOpena11y bug
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
openedx/frontend-app-authoring#3309 ·
Maintainers usually reply within 1 day
-
Course Outline card tag-count badge stays stale after editing tagsPossibly taken @akshaygaur2407 claimed this 8 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
openedx/frontend-app-authoring#3308 · 2 comments ·
Maintainers usually reply within 1 day
-
XBlockStatus small status text uses a default color role below 4.5:1 on the light cardMay be free again @nisatsama claimed this 47 days ago, and no pull request is open. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
openedx/frontend-app-authoring#3282 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
openedx/frontend-app-authoring#3274 ·
Maintainers usually reply within 1 day
All issues in openedx/frontend-app-authoring
Similar issues
-
type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
db-ux-design-system/core-web#8856 ·
Maintainers usually reply within 1 day
-
'!' breaking change is lost when the commit also has an empty BREAKING CHANGE footerPossibly taken @wittdennis claimed this today. Openpriority: p3 type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
googleapis/release-please#2971 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 87/100
Maintainers usually reply within 1 day
-
🛠️ dette technique
Difficulty 2/5 1-3 hours Newbie friendliness 61/100
betagouv/mon-entreprise#4752 · 1 comment ·
Maintainers usually reply within 5 days