openedx / openedx/openedx-core
Push more logic down from openedx-platform into openedx_content
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 10
- Forks
- 32
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 12
Description
Content Libraries API, in particular -- much of this could be in openedx_content
ContainerMetadata could be moved down
Does this mean making openedx-core depend on opaque-keys?
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 locating the Content Libraries API and ContainerMetadata definitions in openedx-core, then compare their responsibilities with openedx_content and investigate whether openedx-core needs to depend on opaque-keys. Done means the intended logic boundaries and dependency change are agreed and the affected code is moved accordingly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- django, python
- Domain
- backend-api-design
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100