openedx / openedx/openedx-platform
Audit these toggles which were previously implicit feature flags
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 8.2k
- Forks
- 4.4k
- Avg merge
- 6d 18h
- Merged PRs (30d)
- 42
Description
These toggles (link coming soon) were previously read from calls to FEATURES.get(...) without any definition in envs or using openedx-toggles. They are now defined in openedx/envs/common.py so that we can drop the FEATURES passthru dictionary.
The toggle_creation_date is a lie/estimate. Use git-blame to correct it.
Should they still exist? Should we DEPR any of them?
Is the description correct? I had Claude auto-generate each one from its usage context.
Is the use case correct? I just put open_edx
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 in openedx/envs/common.py and locate the toggles now defined there, then find their former FEATURES.get(...) call sites. Use git-blame to verify each toggle_creation_date and review the usage context for its description and use case. Done means every toggle has an evidence-based audit outcome, including whether it should remain or be deprecated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100