Default to template field ID for parsed issue body key

[ncalteen]

By default, when an issue body is parsed, the action will now attempt to match the header in the issue body markdown with the label field of the issue template. If found, it will check if an ID is present for that field. If present, the ID will be used for the property key. Otherwise, the action reverts to the original behavior (slugifying the field label).

E.g. If the field looks like this in the template:

  - type: input
    id: name
    attributes:
      label: The Name of the Thing
      description: The name of the thing you want to create.
      placeholder: this-is-the-thing
    validations:
      required: true

Then the parsed issue body will loo like this:

{
  "name": "Whatever the user-provided value is"
}

Otherwise, if the field looks like this in the template

  - type: input
    attributes:
      label: The Name of the Thing
      description: The name of the thing you want to create.
      placeholder: this-is-the-thing
    validations:
      required: true

Then the parsed issue body JSON will look like:

{
  "the_name_of_the_thing": "Whatever the user-provided value is"
}

[github-actions]

🦙 MegaLinter status: ✅ SUCCESS

Descriptor	Linter	Files	Fixed	Errors	Elapsed time
✅ ACTION	actionlint	5		0	0.03s
✅ JSON	jsonlint	21		0	0.17s
✅ JSON	npm-package-json-lint	yes		no	0.34s
✅ JSON	prettier	21		0	0.87s
✅ JSON	v8r	21		0	20.11s
✅ MARKDOWN	markdownlint	1		0	0.8s
✅ MARKDOWN	markdown-link-check	8		0	1.59s
✅ REPOSITORY	checkov	yes		no	14.03s
✅ REPOSITORY	gitleaks	yes		no	0.52s
✅ REPOSITORY	git_diff	yes		no	0.01s
✅ REPOSITORY	grype	yes		no	13.68s
✅ REPOSITORY	secretlint	yes		no	0.86s
✅ REPOSITORY	trivy	yes		no	65.14s
✅ REPOSITORY	trivy-sbom	yes		no	1.1s
✅ REPOSITORY	trufflehog	yes		no	11.96s
✅ TYPESCRIPT	eslint	11		0	8.24s
✅ TYPESCRIPT	prettier	11		0	1.93s
✅ YAML	prettier	20		0	0.73s
✅ YAML	v8r	20		0	29.29s
✅ YAML	yamllint	20		0	0.3s

See detailed report in MegaLinter reports

MegaLinter is graciously provided by