openedx / openedx/frontend-app-authoring
Create Library page needs better messaging for conflicting org/slug
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 17
- Forks
- 218
- Avg merge
- 9d 20h
- Merged PRs (30d)
- 20
Description
Steps to reproduce
- Go to the Libraries (Beta) listing and make note of a library that exists
- Go to the "+ New Library" page
- Try to create a library with the same org and org slug
Related issues / open questions
- (haven't tested) does the same issue happen if you choose an org doesn't exist when
ORGANIZATIONS_AUTOCREATE == False? - These same behaviors are issues on the Create Legacy Library page
Actual
Expected
This should cause an error, but it should be a user-friendly error banner instead of a dev-oriented error message.
Contributor 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.
Research direction
Start by reproducing the conflict on the Libraries (Beta) listing's "+ New Library" page with an existing organization and slug, then trace the Create Library flow to where the developer-oriented error is displayed. Done means a user-friendly error banner appears for this conflict, with the related behavior on the Create Legacy Library page and the ORGANIZATIONS_AUTOCREATE == False case investigated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- frontend, web-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100