Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Date/Time Component Fails to Save When 'noeval' Property is Set to True #5637

Closed
oupa-mboyane opened this issue Jun 7, 2024 · 1 comment
Closed
Assignees

Comments

@oupa-mboyane
Copy link

Description:
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.

Implementation Context:
<form-builder [form]="form" (change)="change()" [options]="formOptions" [noeval]="true"></form-builder>

Version/Branch
4.19.2

To Reproduce
Steps to reproduce the behavior:

  1. Create a form using the form builder in an Angular project.
  2. Drag and drop a Date/Time component into the form.
  3. Go to the Date section of the Date/Time component.
  4. Enter the date you want to exclude in the 'Disable specific dates or dates by range' field or leave it blank.
  5. 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.

Screenshots
Screenshot 2024-06-07 122018

Additional context
Workaround: When the noeval property is set to false, the form saves without any error alerts.
Rolling back to version 4.15.1 seems to work without encountering this issue.

Please investigate this issue and provide a fix.

@ZenMasterJacob20011
Copy link
Contributor

Closing due to duplicate ticket

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants