Data loss when switching among template editor tabs
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- react
- Domain
- frontend
Research direction
Start by reproducing the scenario in the template editor: delete a code block, switch to the Test Data tab, return to the HTML tab, and try Undo. Trace how each tab preserves editor state and undo history. Done means the deletion can be undone after switching tabs, without losing the existing tab behavior.
Written by the indexing model from the issue text.
Description
Scenario:
- Debug a template, run into an error
- Delete the offending code block.
- Encounter a different, earlier, error (which is odd but another issue - #377), about substitution values
- Go to the Test Data tab to check the substitution values
- Come back to the HTML tab
- Try to Undo the deletion of the code block from step 2.
Result: no undo. The code block is lost.
I expect a template editor with syntax highlight to behave like a code editor, and offer basic undo.
- Dominant language
- API Blueprint
- Stars
- 18
- Forks
- 9
- Avg merge
- 2d 5m
- Merged PRs (30d)
- 8
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from SparkPost/developers.sparkpost.com
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
SparkPost/developers.sparkpost.com#501 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 32/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
All issues in SparkPost/developers.sparkpost.com
Similar issues
-
needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 61/100
rjsf-team/react-jsonschema-form#5495 ·
Maintainers usually reply within 2 days
-
accessibility good first issue
Difficulty 1/5 1-3 hours Newbie friendliness 92/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
johnwalley/allotment#913 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day