Three suggested improvements for failure reporting
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
No files, tests, or entry points are named in the issue. Start by locating the command's existing failure-reporting flow, then define the scope and acceptance criteria for reporting only failed imports, writing reports to a file, and retrying failed items without re-importing the full export.
Written by the indexing model from the issue text.
Description
Enhancement suggestion:
-
Add option for just failed imports to be reported (typically media I guess?)
-
Allow for this report to dumped to a file
-
Allow for this report to be parsed to attempt a re-import of failed items without needing to re-import the full initial export file just to add the missing items
- Dominant language
- PHP
- Stars
- 22
- Forks
- 23
- Avg merge
- 5m
- Merged PRs (30d)
- 1
Contributor 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.
Similar issues
-
a11y admissions.uiowa.edu needs grooming SiteImprove best practice
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Save States Menu Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
pluginsGLPI/datainjection#673 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
octobercms/october#6130 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
getgrav/grav-plugin-form#656 ·