![]() Similar labels may be processed into identical references. If you want to distinguish the fields in the resulting issue, you should use distinct label attributes. Id attributes are not visible in the issue body. name: "Bug report" body: - type: textarea id: name_1 attributes: label: Name - type: textarea id: name_2 attributes: label: Name If duplicate label attributes are required, you can supply at least one id to differentiate two elements with identical labels. Input fields can also be differentiated by their id attribute. name: "Bug report" body: - type: textarea attributes: label: Name - type: textarea attributes: label: Operating System The error can be fixed by changing the label attribute for one of the input fields to ensure that each label is unique. Example of "body must have unique labels" error name: "Bug report" body: - type: textarea attributes: label: Name - type: textarea attributes: label: Name When there are multiple body elements that accept user input, the label attribute for each user input field must be unique. name: "Bug report" body: - type: input id: name attributes: label: First name - type: input id: surname attributes: label: Last name Body must have unique labels The error can be fixed by changing the id for one of these inputs, so that every input field has a unique id attribute. Example of "body must have unique ids" error name: "Bug report" body: - type: input id: name attributes: label: First name - type: input id: name attributes: label: Last name If using id attributes to distinguish multiple elements, each id attribute must be unique. name: "Bug report" body: - type: markdown attributes: value: "Bugs are the worst!" - type: textarea attributes: label: "What's wrong?" Body must have unique ids The error can be fixed by adding non-markdown elements that accept user input. ![]() Example of "body must contain at least one non-markdown field" error name: "Bug report" body: - type: markdown attributes: value: "Bugs are the worst!" A markdown element is static text, so a body array cannot contain only markdown elements. Issue forms must accept user input, which means that at least one of its fields must contain a user input field. Body must contain at least one non-markdown field The error can be fixed by removing the forbidden keys. Y, Y, yes, Yes, YES, n, N, no, No, NO, true, True, TRUE, false, False, FALSE, on, On, ON, off, Off, OFF To avoid this, we have explicitly forbidden the usage of the following keys: YAML parses certain strings as Boolean values. The error can be fixed by removing the unexpected keys. For more information about which top-level keys are supported, see " Syntax for issue forms." Example of " input is not a permitted key" error name: "Bug report" hello: world. input is not a permitted keyĪn unexpected key was supplied at the top level of the template. name: "Bug Report" description: "File a bug report". If the field is not required, you should delete the key-value pair. The error can be fixed by correcting the value to be a non-empty string. name: "" description: "File a bug report" assignees: " ". Įmpty strings, or strings consisting of only whitespaces, are also not permissible when the field expects a string. For example, strings that contain ' must be wrapped in double quotes. Strings may need to be wrapped in double quotes to be successfully parsed. The error can be fixed by providing a string as the value. The description below is being parsed as a Boolean, but it should be a string. This error message means that a permitted key has been provided, but its value cannot be parsed as the data type is not supported. name: "Bug report" description: "Thank you for reporting a bug!". The error can be fixed by adding name as a key. Example of "required top level key name is missing" error description: "Thank you for reporting a bug!". The template does not contain a name field, which means it is not clear what to call your issue template when giving users a list of options. Note: Issue forms are currently in beta for only.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |