openedx / openedx/openedx-platform
Merge XBlockRuntime into OpenedXContentRuntime
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 8.2k
- Forks
- 4.4k
- Avg merge
- 6d 18h
- Merged PRs (30d)
- 42
Description
OpenedXContentRuntime is based on XBlockRuntime, but XBlockRuntime isn't used for anything else.
There could instead just be OpenedXContentRuntime, based on xblock.core.Runtime + RuntimeShim. The two modules (runtime.py, openedx_content_runtime.py) could be merged into one as well.
Discussion: https://github.com/openedx/openedx-platform/pull/38011#discussion_r2824166935
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 with runtime.py and openedx_content_runtime.py, then read the linked pull request discussion for the rationale and constraints. Check whether XBlockRuntime has any remaining uses before consolidating it into OpenedXContentRuntime based on xblock.core.Runtime and RuntimeShim. Done means the duplicate runtime module is removed or merged and all references continue to work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100