biocompute-objects / biocompute-objects/portal_userdb

The "Save draft BCO" button only saves user's edits if the user clicks "Next"

Open
#498 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
1
Forks
1
Avg merge
10m
Merged PRs (30d)
1

Description

**Describe the bug**
The "Save draft BCO" button only saves user's edits if the user clicks "Next" at the top of the page being edited and reaches the last page (Tree View). Otherwise, if the user edits a page and clicks "Save draft BCO" right away, the edits are not saved.

**To Reproduce**
Steps to reproduce the behavior:
1. Go to a BCO, e.g. GLY_000024
2. Click on any section in the sidebar, e.g. Raw JSON View
3. Make any edits
4. Click "Save draft BCO" in the sidebar
5. Refresh
6. Go to Raw JSON View and find the page unchanged
7. Make any edits
8. Scroll to top and click Next until it's greyed out
9. Click "Save draft BCO" in the sidebar
10. Refresh
11. Now your edits have been saved

**Expected behavior**
The necessary steps should just be this:
1. Go to a BCO, e.g. GLY_000024
2. Click on any section in the sidebar, e.g. Raw JSON View
3. Make any edits
4. Click "Save draft BCO" in the sidebar
5. Refresh
6. See that the changes have been saved

**Desktop (please complete the following information):**
- OS: Windows 10
- Browser: Edge
- Version: 133.0.3065.82

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the issue in a BCO such as GLY_000024: edit a section, click “Save draft BCO” without using “Next,” refresh, and verify whether the edit persists. Compare this with saving after advancing through the pages. Done means edits from any sidebar section persist immediately after clicking “Save draft BCO.”

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.