Skip to content

New Milestone tasks causes setter error #26

Description

@jjsibborn

I have turned off autoSave on the Editor (autoSave={false}) so the user can manually save the task. When they

  • Create a new task
  • Edit the task and change it to a 'Milestone' type
  • Save the task
Image

is causes a javascript error

Image

This is relating to the function in editor.js

Image

Should the forEach function include a check if ed is defined - or any other alternative?

ie

      fields.forEach((ed) => {
            if (!ed) return;

            if (ed.setter) ed.setter(out, values[ed.key]);
            else out[ed.key] = values[ed.key];
      });

Note: It does work if you change any other inputs after you change the milestone, or you change the milestone back to Task then to Milestone again

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions