Date label not in label JSON

[bcazeaux]

Describe the bug

Today, when adding a new DateTime input into a form, it is possible to set a Date Label. Meanwhile, the date label is stored in the json with a "dateLabel" key while a "label" key stays with the default value "datetime". This behavior apply only to DateTime input.

Should the label be directly stored in the label key ?

Steps to reproduce

1. Add a DateTime input
2. Change the default label
3. Your JSON file should look like that :
   {
   "subtype": "date",
   "dateLabel": "myCustomLabel",
   "label": "Date time",
   "type": "datetime",
   "layout": {
   "row": "Row_1d1o9f4",
   "columns": null
   }

Expected behavior

The JSON should look like :
{
"subtype": "date",
"label": "myCustomLabel",
"type": "datetime",
"layout": {
"row": "Row_1d1o9f4",
"columns": null
}

Environment

• OS: Windows 10
• Camunda Modeler Version: 5.24.0
• Execution Platform: Camunda 7.19
• Installed plug-ins: None

Additional context

No response

---

Depends on bpmn-io/form-js#1268

[nikku]

@bcazeaux Could you provide more context? Do you use a generated form or Camunda Form? How can we reproduce the issue (from the start, not from Add a DateTime input)?

[bcazeaux]

I'm using a Camunda Form created from the camunda modeler from a new file

[nikku]

Thanks. Pending clarifications internally. I forwarded this issue.

[vsgoulart]

Hi @bcazeaux , thanks for reporting this

The property label is basically not used on anything and it's only there by a mistake because of a similar implementation with other component.

I created an issue on the form-js repos

@nikku I believe we can close the issue on this repo

[nikku]

@vsgoulart We'll leave the issue open and clearly link it to your upstream bug report.

[bcazeaux]

And for my record, why using "dateLabel" instead of "label" like every other component ?

[vsgoulart]

And for my record, why using "dateLabel" instead of "label" like every other component ?

@bcazeaux It's just an implementation detail of the the datetime component. Under the hood it's always the same component if we render the time input or not so it always uses dateLabel