Document: a component cannot be placed inside its own subtree (422)
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 78/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Domain
- documentation
Research direction
Start with the API component positions and component groups pages under content/4.api/, then check how those pages describe writes and validation errors. Document the listed 422 cases, including draft and published components, allowed sharing, and existing cycles; done when the pages explain each behavior and its stated scope.
Written by the indexing model from the issue text.
Description
The API bundle now refuses any write that would place a component inside its own subtree (components-web-app/api-components-bundle#503, fixes components-web-app/api-components-bundle#502).
Please document under the API component positions and component groups pages (content/4.api/):
- A
ComponentPositionwhosecomponentcontains the targetcomponentGroup, at any depth, is a 422 with a violation oncomponent: "The component cannot be placed in the component group<reference>: the group is inside the component." This applies toPOST /_/component_positions, aPATCHof a position'scomponentorcomponentGroup, and positions embedded in a component write (componentPositions[i].component). - Giving a
ComponentGroupan owner (components) from inside that group's own subtree is a 422 oncomponents: "The component group<reference>cannot be owned by a component inside it." - A published component and its draft count as one component, so placing a container's draft inside the published container (or the reverse) is refused too.
- Sharing one component in several places (for example, two sibling containers) is still allowed. Only a path back to itself is refused.
- Existing positions are not re-checked when unrelated fields change, so content already holding a cycle (from fixtures or SQL) can still be read and edited. Reads (security voter, manifest) terminate on it.
The module side (disabling the option with a reason before sending) is cwa-nuxt-module#157.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- Avg merge
- 1h 20m
- Merged PRs (30d)
- 1
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 components-web-app/docs
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
components-web-app/docs#260 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
components-web-app/docs#258 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
components-web-app/docs#257 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
components-web-app/docs#256 · 1 comment ·
-
Difficulty 1/5 1-3 hours Newbie friendliness 78/100
components-web-app/docs#253 ·
All issues in components-web-app/docs
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
OpenPetsHQ/openpets#273 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
fritzprix/libr-agent#2161 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
blackboardsh/electrobun#581 ·
-
backlog-skill effort:xs frontend infra ready-for-agent
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
LucasSantana-Dev/Lucky#2862 ·
Maintainers usually reply within 1 day