Treat Mustache "info" message as info, not problem #274
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The Mustache lint seems to treat all HTML validation messages as problems, even if they are "info".
I have run into this recently, while checking my course format plugin. I guess there's been a recent change to the HTML validator that's caused it? A Mustache file failed validation because some included Moodle Mustache files closed HTML single tags with /> instead of just >. I got the "info" message "Trailing slash on void elements has no effect and interacts badly with unquoted attribute values." As far as I can tell, this message is only ever given when there is no actual problem, and if there is an actual problem with a trailing /, I think another, non-info message will likely be given.
I don't think it's necessary to treat "info" messages as problems, and I suspect it will now cause most course format plugins to fail validation in a way that's beyond the author's control. (Not sure about other plugin types.)
I think the suggested change should fix the issue, but I haven't actually figured out how to run it locally to check, so I don't really know.
I assume this plugin is used for GitHub actions, and the Moodle code prechecks? If so, and this change is accepted, could you tell me how long it's likely to be before those use the update?