[BUG] Date/Time Component Fails to Save When 'noeval' Property is Set to True
@ZenMasterJacob20011 is already working on this.
Since Jul 3, 2024.
Assessment
This issue has not been assessed yet.
Description
Environment
When using the noeval property set to true in the component within an Angular project, the Date/Time component fails to save. This issue occurs consistently and prevents the proper saving of the form. An error alert is shown with the message: "Please fix the following errors before submitting. Disable specific dates or dates by range: custom." The error is shown in the attached screenshot. However, the form saves without the error alert if noeval is set to false.
- Hosting type
- Form.io
- Local deployment
- Version:
5.3.0
- Version:
- Formio.js version:
4.19.2 - Frontend framework: Angular
- Browser: Chrome
- Browser version:
Steps to Reproduce
- Create a form using the form builder in an Angular project.
- Drag and drop a Date/Time component into the form.
- Go to the Date section of the Date/Time component.
- Enter the date you want to exclude in the 'Disable specific dates or dates by range' field or leave it blank.
- Click Save on the preview screen on the right.
Expected behavior
The Date/Time component should save, even when the noeval property is set to true.
Observed behavior
The Date/Time component does not save, when you click save, an error alert is displayed with the message: "Please fix the following errors before submitting. Disable specific dates or dates by range: custom."
Code Implementation
<form-builder [form]="form" (change)="change()" [options]="formOptions" [noeval]="true"></form-builder>
Screenshot
Additional Information:
Workaround: When the noeval property is set to false, the form saves without any error alerts.
Rolling back to Formio.js version 4.15.1 seems to work without encountering this issue.
- 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