How to better understand data mutation/augmentation in runtime

Open
#193 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
python

Research direction

The issue names no files, tests, or entry points. Start by tracing the runtime pipeline responsible for data mutation and augmentation, then clarify whether the intended outcome is documentation or debugging support; the issue does not define what completion looks like.

Written by the indexing model from the issue text.

Description

enhancement

Description

Some comments I've gathered from the community survey on the challenges/suggestions section:

Some challenges with local development, debugging ... and the standard learning curve. Since the code being executed is several layers away, it sometimes becomes difficult to debug the pipeline and understand the data mutation/ augmentation happening along the way.

Dominant language
Python
Stars
10
Forks
30
Avg merge
5h 49m
Merged PRs (30d)
5

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from openedx/openedx-filters

All issues in openedx/openedx-filters

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.