Enhancement: Add multiline string field support in data view

[davidsneighbour]

I would expect the Dashboard > Data view to work according to the docs for field configurations for strings, as in single: false and wysiwyg: true resulting in extended text fields. It doesn't though.

Config:

  "frontMatter.data.files": [
    {
      "id": "music2program2",
      "title": "Music to program to",
      "file": "[[workspace]]/data/dnb/kollitsch/music.json",
      "fileType": "json",
      "labelField": "name",
      "schema": {
        "title": "music2program2",
        "type": "object",
        "required": [
          "name",
          "link"
        ],
        "properties": {
          "name": {
            "type": "string",
            "title": "Name"
          },
          "link": {
            "type": "string",
            "title": "URL"
          },
          "description": {
            "type": "string",
            "title": "Description",
            "single": false,
            "wysiwyg": true
          }
        }
      }
    }
  ],

results in:

It would be nice to have at least a multiline field here. Maybe even globally some form of distinction between string and "multiline string" as field type in general?

Desktop (please complete the following information):

• OS: Ubuntu 22.04

[davidsneighbour]

also sidenote: "your $title data items" will probably result in weird displays sometimes. Because the left column is always visible it would be nice to just have "data items" or even "items" as column title here and "Create or modify data" in the third column. The second column could be wider, the first one smaller.

[estruyf]

@davidsneighbour single and wysiwyg are not supported. The files are automatically rendered by the JSON schema and do not follow the same logic as the other content fields (yet). I'm going to tag this as an enhancement.

[davidsneighbour]

Ping :)

I just worked on my data file configuration and was about to open a new issue when I realized that I had already done so a while back.

The issues remain:

• from the view, there is no need to have "your $title data items" (it takes too much space and is understood from the left column). "Select your data type", "Items", and "Create or Modify data" would result in a single header line instead of 1 to 3 in the screenshot below.
• a multiline field would be really nice ;) my description in this specific case is a markdown text that might be long.

new idea ;):

• validation. the slug field here should not have spaces or special characters, so it would be nice to maybe have some form of a regular expression to match the content of each field against.

This still stays enhancement, so there is no pressure :) but I got ideas for the data functionality. Think recipes or "trading card games". I think it might be a powerful feature for data file enabled SSGs.

[michaeltlombardi]

I have a strong need for multiline fields as well (also using markdown in those fields).

[estruyf]

I heard both of you 😀

To support this, I must add a new property for the long text (textarea) field.

{
  "name": {
    "type": "string",
    "title": "Name"
  },
  "url": {
    "type": "string",
    "title": "URL"
  },
  "description": {
    "type": "string",
    "longtext": true,
    "title": "Description"
  }
}

Above I used longtext (as that is the field to load in uniforms, but if you have a better suggestion, let me know.

[michaeltlombardi]

That's fine! As long as it's documented, I can work with it (multiline might be a more intuitive key name but I'm not too fussed about it).

[estruyf]

and so it became multiline.

@davidsneighbour @michaeltlombardi you can configure it as follows:

{
  "name": {
    "type": "string",
    "title": "Name"
  },
  "url": {
    "type": "string",
    "title": "URL"
  },
  "description": {
    "type": "string",
    "multiline": true, // Set the multiline support
    "title": "Description"
  }
}

[davidsneighbour]

The label of the field is not bold like on the other fields. All else is as I dreamed of :)