Make Runtime Services Plugin-able
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 470
- Forks
- 231
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 6
Description
Handwavey Sketch:
- Use stevadore to register/lookup installed plugin implementations (plugins for the 'i18n' service would be registered under the entry_point key 'xblock.service.i18n', and would be named for their function ['null', 'django', etc])
- XBlock runtime should look for services in the following order:
- Explicitly provided in the
serviceskwarg - Enabled entry_point plugins in the provided services configuration dictionary, configured by that same dictionary
- Default plugins registered with stevadore (maybe?)
- Explicitly provided in the
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 tracing XBlock runtime service lookup from the services kwarg and the services configuration dictionary. Review the proposed xblock.service.i18n entry-point naming and stevadore registration flow; done means the lookup order is defined and supports explicit services, configured plugins, and default plugins.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100