Make section ordering consistent in output
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 30/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- python
- Domain
- documentation
Research direction
The issue names no file, test, or entry point. Inspect the documentation generator's section-ordering and output-generation paths, then reproduce the result with the same sections supplied in different input orders; done means the generated output uses one predictable ordering every time.
Written by the indexing model from the issue text.
Description
Regardless of input order, we want section predictably ordered in output.
- Dominant language
- Python
- Stars
- 20
- Forks
- 25
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 boostorg/docca
-
Difficulty 3/5 1-2 days Newbie friendliness 38/100
-
Type aliases with template parameters are rendered wrongMay be free again @evanlenz claimed this 1311 days ago, and no pull request is open. Open
-
very confused output, and unsure whyMay be free again @evanlenz claimed this 1484 days ago, and no pull request is open. Open
-
"Edit this page" linkMay be free again @evanlenz claimed this 1642 days ago, and no pull request is open. Open
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
Similar issues
-
needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
json_params_matcher fails on falsy top-level JSON primitives (0, False, "")Possibly taken @mayureshsonawane17 claimed this today. OpenWaiting for: Product Owner
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 5 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Add .devin pluginOpen
Difficulty 1/5 Under an hour Newbie friendliness 88/100
ayghri/i-have-adhd#249 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
modelscope/FunASR#3762 ·
Maintainers usually reply within 1 day