Skip to content

Calculation rule "default on error" doesn't work for list-valued properties #12

Description

If a calculation throws an error, the defaultIfError option is used as the property value instead, which has a default value of null. This isn't a valid value for list-valued properties, and it results in an error: "Cannot read property 'length' of null".

Should we...

  • Use the property default instead?
  • Use a data-type default?
  • Use [] for list-valued properties, and null for others?

On a related note, it might be good for canSetValue to return false if you try to set a list-valued property to null (since that will also result in cryptic unhandled errors for the same reason).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    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