forms that intentionally reuse a key with mutually exclusive conditionals
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 64/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- react, typescript
- Domain
- frontend
Research direction
Reproduce the issue with the two mutually exclusive name fields in the report, using a blank submission. Start by tracing the visibility check and clearComponentOnHide() behavior described in the issue, then follow how deleteValue() affects the shared key. Done means entering a valid name no longer clears the shared value or triggers the required-field validation message.
Written by the indexing model from the issue text.
Description
Describe the bug
I was using Formio/React 5.3.0 but when I upgraded to 6.2.1 I found that duplicate key reuse for mutually exclusive conditions always throws validation error.
In @formio/react 5.3.0 (formiojs 4), clearOnHide only runs when visibility changes:
if (this.visible !== visible) {
this.visible = visible; // setter may clear
}
Once the edit field is already hidden, later condition checks leave data.name alone, so the create field keeps working.
In @formio/react 6.2.1 (@formio/js 5), every condition check clears a hidden field:
if (this.visible !== visible) {
this.visible = visible;
}
this.clearComponentOnHide(); // always, while hidden
So on create, the hidden edit name repeatedly does deleteValue() on the shared data.name. The create field then fails required, and customMessage makes it look like the pattern error.
below is my two components with the same name but conditional:
{
"key": "name",
"type": "textfield",
"input": true,
"label": "Name",
"disabled": true,
"validate": {
"pattern": "^[a-zA-Z0-9\\s]*$",
"required": true,
"maxLength": 80,
"customMessage": "Invalid name; must contain only letters, numbers or spaces "
},
"autofocus": true,
"tableView": true,
"spellcheck": false,
"showCharCount": true,
"customConditional": "show = data.submissionUuid.length > 0",
"hideOnChildrenHidden": false
},
{
"key": "name",
"type": "textfield",
"input": true,
"label": "Name",
"validate": {
"pattern": "^[a-zA-Z0-9\\s]*$",
"required": true,
"maxLength": 80,
"customMessage": "Invalid name; must contain only letters, numbers or spaces "
},
"autofocus": true,
"tableView": true,
"spellcheck": false,
"showCharCount": true,
"customConditional": "show = data.submissionUuid.length === 0",
"hideOnChildrenHidden": false
}
To Reproduce
Steps to reproduce the behavior:
- create a form with customConditionals has shown above
- use that form with a Form component with no submission data or a blank object.
- on entry of the name you will always get the customMessage.
Expected behavior
I would expect it not to deleteValue() on the shared data.name so we will not get a custom validation message if the text entered is valid.
Screenshots
here is a screen shot of what i with mutually exclusive conditionals
- Dominant language
- TypeScript
- Stars
- 371
- Forks
- 309
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the 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/react
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
-
onChange `modified` property remains false when file component is updatedMay be free again @ZenMasterJacob20011 claimed this 295 days ago, and no pull request is open. Open
-
FormBuilder onChange callback not triggered when options prop is providedMay be free again @Victoriya25 claimed this 337 days ago, and no pull request is open. Open
-
FormBuilder with OnChange broke textareaMay be free again @lane-formio claimed this 309 days ago, and no pull request is open. Open
-
Difficulty 3/5 1-2 days Newbie friendliness 30/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