š derive: the "start a list roll-up one rung up" idiom, since a type cannot `copy` its own `id` into its own field
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 82/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- python
- Domain
- documentation
Research direction
Read the derive documentation section for the copy kind and the existing collect chain example. Add a short example showing a list roll-up that starts one rung up, with a sentence explaining why a type cannot copy its own id into its own field. Done when both the example and explanation appear beside the existing chain example.
Written by the indexing model from the issue text.
Description
What happens
The derive kind copy of id into an array field is refused on the type whose own ids are wanted (both tools, same reason), so a list roll-up of requirement ids has to start one rung down: on a demo project chain_reqs is a copy of id over satisfies with select = "list" on the architecture type, then a collect on every rung below. That is the right idiom, and nothing in the derive documentation says so.
What to do
A short "start a list roll-up one rung up" example under the copy kind (and a sentence on why a type cannot copy its own id into its own field), beside the existing collect chain example.
- Dominant language
- Python
- Stars
- 309
- Forks
- 103
- Avg merge
- 4h 40m
- Merged PRs (30d)
- 154
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 useblocks/sphinx-needs
-
bug pkg: sphinx-needs
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
useblocks/sphinx-needs#2338 Ā·
Maintainers usually reply within 1 day
-
bug pkg: sphinx-needs
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
useblocks/sphinx-needs#2335 Ā·
Maintainers usually reply within 1 day
-
š needs.json per-id files say needs_defaults_removed with no needs_schema and nothing left outOpenbug pkg: sphinx-needs
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
useblocks/sphinx-needs#2332 Ā·
Maintainers usually reply within 1 day
-
š the "own service" example in docs/services/index.rst cannot be registeredPossibly taken @chrisjsewell claimed this 10 days ago. Opendocumentation pkg: sphinx-needs
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
useblocks/sphinx-needs#2327 Ā·
Maintainers usually reply within 1 day
-
bug pkg: sphinx-needs
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
useblocks/sphinx-needs#2325 Ā·
Maintainers usually reply within 1 day
All issues in useblocks/sphinx-needs
Similar issues
-
area/profiles comp/cli P3 type/feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
NousResearch/hermes-agent#146372 Ā·
Maintainers usually reply within 1 day
-
[BUG] OpenAI-compatible embedding model alias breaks embedder constructionPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
[oblt-aw][autodoc] Document obs-aw-automerge contract and fix automerge doc inconsistenciesPossibly taken @github-actions claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
GeoSeries scale and skew tests fail with pytest 9.2.0Possibly taken @jiayuasu claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
admission-deferred priority: medium status: ready work-class: scoped
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
melodic-software/claude-code-plugins#10887 Ā· 4 comments Ā·
Maintainers usually reply within 1 day