openedx / openedx/frontend-app-authoring
When creating a new library component, allow non-ascii characters in the URL key
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 17
- Forks
- 218
- Avg merge
- 9d 20h
- Merged PRs (30d)
- 20
Description
Currently, when you create a new Unit/Subsection/Section, and you give it a title containing only non-ascii characters:
you get that title reflected in the container's URL:
e.g. http://.../authoring/library/...:unit:αθήνα-587b00
But this doesn't yet work for creating new text/problem/video components: although you can set the title before they are saved, they always get a random UUID in the URL. (Unless you then copy and paste them, which gives you a friendly slug that works with unicode characters).
Change either the backend as required so that new text/problem/video components can use non-ascii letters in their friendly URL codes/slugs, just like containers do, and just like copy-paste does.
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
Trace the creation flow for new text, problem, and video components, then compare its URL-code generation with containers and copy-paste behavior. The change is complete when titles containing only non-ASCII letters produce friendly URL codes instead of random UUIDs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100