How to add a wrapper text (prefix and suffix) to the issue template's form element in YAML configuration?

[MurzNN]

I need to wrap a text, that is entered into the issue form's Textarea, by custom text (prefix and suffix), but can't find a way how to do this?

For example, I want to automatically hide a form element for long texts under collapsed <details> section, like this: https://gist.github.com/pierrejoubert73/902cc94d79424356a8d20be2b382e1ab - how to do this?

[mfisher87]

I feel this feature would be very valuable for conda-forge's issue templates. When people open a bug against a feedstock, we ask them to paste the output of some commands, including a full accounting of packages installed in their environment. In some issues, that text can take up a lot of space, and I'd love to have it collapsed into a <details> tag automatically as configured by e.g. a render_template field in the YAML:

render_template: "<details><summary>Output of `conda list`</summary>{{response}}</details>"

[mdempsky]

The Go project would like this feature. We ask users to provide go env output because it's sometimes useful, but this pushes the more interesting text from the user's issue report below the fold, which then makes triage more tedious as we need to scroll up and down more.

[zhangt2333]

My workaround (provide a default value):

  - type: textarea
    id: log
    attributes:
      label: Log
      description: |
        Provide the log output.
        _Note:_ You can paste the `output/tai-e.log` file into the placeholder below. If it is too long, you can attach it as a file.
      value: |
        <details>
          <summary>Click here to see Log</summary>
          <!-- Please leave one blank line below for enabling the code block rendering. -->

          ```
          The content of 'output/log.txt' file
          ```
        </details>
    validations:
      required: true

[leccelecce]

Has anyone found any better solution to this? I'm surprised it's not more upvoted, I'm getting index-finger-curl from scrolling through issues with pages of logs, config etc required by projects to investigate issues....