[Custom Components] Multiple component schema info showing more than one component rather than allowing an array of values to be captured.
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- angular, typescript
- Domain
- frontend
Research direction
Start at the custom component registration and its JSON schema, then reproduce the select component with multiple enabled. Check how the schema's multiple option affects rendering and value validation; done means selected values are captured as one array without rendering multiple component instances.
Written by the indexing model from the issue text.
Description
Hello ,
The "multiple":true is acting like I wanted multiple of that component in one space rather than If this component should allow an array of values to be captured.
Wanting to make a custom multiple select component , When I add in the "multiple":true into the object for the component it gets rendered out as :

Yet without it I am getting an error that says the component can not be an array:

In the custom component I have the the multiple option in select set to true , so the component returns the items selected as an array.
This is the custom component I am calling :
Json part :

Registering it :

Note: the comment out schema acts like the "multiple":true, in the Json.
I believe I left something out in registering it but I can not figure out what. I say that because the same behavior is seen when the "multiple":true is added to other components that normally do not return an array.
- Dominant language
- TypeScript
- Stars
- 706
- Forks
- 493
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No 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 formio/angular
-
question
Difficulty 3/5 1-2 days Newbie friendliness 55/100
-
[BUG] <form-builder> move icon is missingMay be free again @PrathameshHegde claimed this 101 days ago, and no pull request is open. Openbug
-
question
Difficulty 2/5 1-3 hours Newbie friendliness 25/100
-
[BUG] "Left (Right-aligned)" label position causes misaligned error messages and descriptionsMay be free again @Victoriya25 claimed this 365 days ago, and no pull request is open. Openbug
-
question
Difficulty 5/5 Over a week Newbie friendliness 25/100
Similar issues
-
`@angular/[email protected]` depends on vulnerable Vite 7.3.7 - GHSA-p4f5-76q4-ffq7 (Critical RCE)Openarea: @angular/build
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
angular/angular-cli#34764 ·
Maintainers usually reply within 1 day
-
status/need-triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
google-gemini/gemini-cli#30384 · 1 comment ·
Maintainers usually reply within 1 day
-
P2
Difficulty 1/5 Under an hour Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
bug ready-for-human
Difficulty 2/5 1-3 hours Newbie friendliness 60/100
LucasSantana-Dev/Lucky#3150 ·
Maintainers usually reply within 1 day
-
enhancement good first issue priority: low size: XS
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day