add issue data when adding singletons
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- full-stack
Research direction
Start by reading the series creation flow and the existing issue skeleton entry flow, especially how the “Is Singleton” option is handled. Determine how the issue-level fields listed in the request could be entered during singleton creation; done means a singleton can be submitted with those details in one step, while non-singleton behavior remains unchanged.
Written by the indexing model from the issue text.
Description
When adding an issue skeleton to a non-singleton series, we can add fields such as Publisher, Brand Emblem, On-Sale Date, Price, Page Count, Bar Code, ISBN, Indicia Printer, Age Rating, etc. However, when adding a new issue that is a singleton, it is a multi-step process as first the series has to be submitted and approved, and then needs it be edited to add all those other details that are essential issue skeleton details. But that means every new one-shot issue has to be submitted and approved in multiple steps, while adding an issue to an existing series only requires one step to add the skeleton details. Is it possible that when adding a new series and the "Is Singleton" option is checked, it unlocks the option to enter issue level skeleton details as well?
- Dominant language
- Python
- Stars
- 122
- Forks
- 36
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 28
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- No 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 GrandComicsDatabase/gcd-django
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
GrandComicsDatabase/gcd-django#859 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
GrandComicsDatabase/gcd-django#881 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
GrandComicsDatabase/gcd-django#880 · 2 comments ·
Maintainers usually reply within 1 day
-
update django-autocomplete-light, or replacePossibly taken @jochengcd claimed this 3 days ago. Open
Difficulty 4/5 3-5 days Newbie friendliness 43/100
GrandComicsDatabase/gcd-django#803 · 2 comments · 1 assignee ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
GrandComicsDatabase/gcd-django#802 ·
Maintainers usually reply within 1 day
All issues in GrandComicsDatabase/gcd-django
Similar issues
-
documentation good first issue priority: P2 status: ready
Difficulty 1/5 Under an hour Newbie friendliness 88/100
RhinoLink-Tech/data-fabric#500 ·
Maintainers usually reply within 1 day
-
backlog
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
EchoTools/nevr-runtime#2384 ·
Maintainers usually reply within 1 day
-
[Bug]: The H2 series' and the H3C's fan 3 is labelled "Chamber Fan", Bambu calls it the exhaust fanOpenarea:ui
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
btclib-org/btclib#3062 ·
Maintainers usually reply within 1 day
-
area:evals area:infra enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
jse-avl/support-bot#4 · 1 comment ·