learningequality / learningequality/studio

Unstable - Trash - The inheritable metadata modal is not displayed when adding a new folder

Open
#4,770 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug DEV: frontend P1 - important TODO: needs decisions
Dominant language
Python
Stars
191
Forks
307
Avg merge
5d 6h
Merged PRs (30d)
10

Description

This issue is not open for contribution. Visit Contributing guidelines to learn about the contributing process and how to find suitable issues.

Observed behavior

If I delete a resource and I go to the Trash to restore it I have an option to add a new folder. When I do so then I don't see the inheritable metadata modal. The modal is also not being displayed if I move the resource to a folder with different metadata.

Expected behavior

Seems that the modal should be displayed if there's metadata added to the parent folder but the expected behavior should be further discussed.

Steps to reproduce the issue

  1. Go to https://unstable.studio.learningequality.org/en/accounts/#/ and sign in
  2. Open a channel with resources withing a folder with metadata
  3. Delete the resource
  4. Go to Trash and attempt to restore the resource by creating a new folder or moving it to a folder with different metadata

Additional information

https://github.com/user-attachments/assets/3bb2cacf-d291-458d-a830-4243ae2b957d

Usage Details

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 Trash restore flow described in the issue, comparing creation of a new folder with moving a resource into a folder with different metadata. Read the behavior introduced by pull request 4635 and clarify the expected modal behavior before identifying the relevant UI entry point; completion requires an agreed behavior and verification in both restore cases.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.