Field-level violations are not shown on multi-valued text and url properties
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 82/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- typescript
- Domain
- frontend
Research direction
Start with TextInput.vue and UrlInput.vue, then trace the status and violations supplied by useStringValueInput.ts; compare the field-level handling with MonolingualTextInput.vue. Reproduce the duplicate-value case in a multi-valued text or url property and confirm that field-level messages appear while per-row messages remain unchanged.
Written by the indexing model from the issue text.
Description
In the subject editor, field-level violations (required, unique) on a multi-valued text or url property are shown nowhere. TextInput.vue and UrlInput.vue pin the field's status to default whenever multiple is set, so CdxField never renders its messages; the per-row messages only cover part-indexed violations. The violations already reach both components through useStringValueInput; only the status binding suppresses them. With error severity the save is blocked with nothing on screen.
Reproduce: give a Schema a text property with "multiple": true and "uniqueItems": { "severity": "error" }, enter the same value twice in a Subject, save.
Expected: the field renders its violation messages, as MonolingualTextInput.vue does (https://github.com/ProfessionalWiki/NeoWiki/pull/1500); per-row messages unchanged.
AI-authored — Claude Code,
Fable 5.1 (max); found while reviewing https://github.com/ProfessionalWiki/NeoWiki/pull/1500 for @JeroenDeDauw, no steering on this text; not yet human-reviewed; cause confirmed by readingTextInput.vue,UrlInput.vueanduseStringValueInput.ts, not reproduced in a browser.
- Dominant language
- PHP
- Stars
- 23
- Forks
- 5
- Avg merge
- 20h 47m
- Merged PRs (30d)
- 107
Contributor guide
No contributing guide indexed for this repository
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 ProfessionalWiki/NeoWiki
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
ProfessionalWiki/NeoWiki#1481 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
ProfessionalWiki/NeoWiki#1180 ·
-
{{#cypher_raw}} and {{#sparql_raw}} results can inject links and categories into the rendering page Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
ProfessionalWiki/NeoWiki#1057 ·
-
UX
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
ProfessionalWiki/NeoWiki#955 ·
-
ECHOLOT feature product
Difficulty 5/5 Over a week Newbie friendliness 25/100
ProfessionalWiki/NeoWiki#1498 ·
All issues in ProfessionalWiki/NeoWiki
Similar issues
-
priority: p3
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
googleapis/librarian#7636 ·
-
0. Needs triage bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
nextcloud/fulltextsearch#1011 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
phpstan/phpstan-doctrine#794 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Automattic/static-site-importer#1767 ·