[BUG] Date/Time Component Fails to Save When 'noeval' Property is Set to True

Ouverte
#1,079 4 commentaires 0 réactions 1 personne assignée Voir sur GitHub

@ZenMasterJacob20011 y travaille déjà.

Depuis le 3/7/2024.

Évaluation

Cette issue n'a pas encore été évaluée.

Description

bug help wanted

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
  • Formio.js version: 4.19.2
  • Frontend framework: Angular
  • Browser: Chrome
  • Browser version:

Steps to Reproduce

  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.

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

Screenshot 2024-06-07 122018

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.

Langage dominant
TypeScript
Étoiles
706
Forks
493
Métriques de merge des PR
Aucune PR mergée en 30 j

Préparer son environnement

  • Aucun Dockerfile ni fichier Docker Compose
  • Propose un modèle de pull request
  • Aucun guide de contribution

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de formio/angular

Toutes les issues de formio/angular

Issues similaires

Plus d'issues TypeScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.