openedx / openedx/frontend-app-authoring

Problem component is created even after clicking Cancel

Open
#3,101 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

needs triage release testing
Dominant language
TypeScript
Stars
17
Forks
218
Avg merge
9d 20h
Merged PRs (30d)
20

Description

Description

When adding a new Problem component in a unit, clicking Cancel does not prevent the component from being created.

The component still appears in the unit after cancelling the creation/editing flow. This may be expected if the component is created immediately when selected, but the behavior is confusing because Cancel usually implies that the action should be discarded.

I'm opening this issue to confirm whether this is the expected behavior or whether cancelling should remove the newly created component.

Steps to reproduce

  1. Go to Course Authoring > Course > Add unit > Add new component.
  2. Open a course unit.
  3. Select Add New Component.
  4. Select Problem.
  5. When the problem editor opens, click Cancel instead of saving.
  6. Return to the unit page.
  7. Check whether the component was created.

Contributor guide

Open the contributing guide

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.

Research direction

Start by reproducing the Course Authoring flow in the issue: add a unit, choose Add New Component, select Problem, then click Cancel. Trace the Problem editor's creation and cancellation entry points to determine when the component is persisted. Confirm with the maintainer whether Cancel should discard the component before changing behavior; done means the agreed cancellation behavior is covered by a regression test.

Written by the indexing model from the issue text.

Assessment

Tech stack
react, typescript
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.