Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Component groups: allowedComponents by component name, and what an empty list means

Closed Beginner friendly
#96 0 comments 0 reactions 0 assignees View on GitHub

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
Tech stack
nuxt, typescript
Domain
documentation

Research direction

Start from the component group documentation and use the CwaComponentGroup examples in this issue as the reference for the recommended syntax. Document CwaComponentNames, all three allowed-components states, validation implications, and the upgrade behavior for groups without a stored list. Done means the docs cover each listed case and the upgrade note accurately.

Written by the indexing model from the issue text.

Description

documentation

Source: components-web-app/cwa-nuxt-module#352 and #351.

What changed

Component names (#352). <CwaComponentGroup :allowed-components> accepts component names as well as collection IRIs:

<CwaComponentGroup reference="main" :location="publishedIri" :allowed-components="[CwaComponentNames.HtmlContent, CwaComponentNames.WatchPastConference]" />
<!-- identical -->
<CwaComponentGroup reference="main" :location="publishedIri" :allowed-components="['HtmlContent', 'WatchPastConference']" />
  • CwaComponentNames (constant) and CwaComponentName (type) are generated from each app/cwa/components/<Name>/<Name>.vue and auto-imported. Editors complete them, and vue-tsc rejects a typo or a removed component.
  • Names are resolved to endpoints at runtime from the API docs. If a name matches no API component, a warning is logged and the group is not synced.
  • Collection IRIs ('/component/html_contents') still work, alone or mixed with names.

Groups with no stored list (#351). Groups created by fixtures or the REST API without a list now receive the template's list on the first signed-in load.

To document

  • Names as the recommended form in the component group docs, with the constant.
  • The three states of the prop:
    • a complete list — must name every type already placed in the group, plus any #[ExplicitAllowOnly] type to offer. A placed type missing from the list fails validation on its next save.
    • omitted — leaves the stored list as it is.
    • null or [] — unrestricted (explicit-only types stay hidden).
  • Upgrade note: groups that never had a list will be PATCHed with the template's list on the first admin load, so check the lists are complete first.
Dominant language
Vue
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Getting set up

We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from components-web-app/docs

All issues in components-web-app/docs

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.