Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Issue with info.md templating

See original GitHub issue

Version of HACS

0.13.0

Describe the bug

A clear and concise description of what the bug is. Template text on the info.md file is sometimes displaying as plain text and not being templated. For example:

Screenshot 2019-08-11 at 20 39 21

When selecting “next” from the drop-down, it applies the template as expected and only displays the text saying that it is the development version.

No error messages appear in the log.

Debug log


Add your logs here.

Issue Analytics

State:
Created 4 years ago
Reactions:1
Comments:10 (5 by maintainers)

Top GitHub Comments

1reaction

ghostcommented, Aug 17, 2019

Hi, @ludeeus

This issue is closed, closed issues are ignored. If you have issues similar to this, please open a seperate issue.

https://github.com/custom-components/hacs/issues/new/choose

And remember to fill out the entire issue template 😃

This message was automatically generated by hacs-bot👾

1reaction

gadgetchnnelcommented, Aug 14, 2019

Interestingly, I just updated HACS to 0.13.1 and now, I see this if 0.13.1 is selected from the dropdown:

Version-0 13 1

but when 0.13.0 is selected it displays correctly like this:

Version-0 13 0

The templating issue was happening previously when 0.13.0 was selected, but not for other versions, so it looks like I am seeing this issue when the version in the dropdown is the same as the currently installed version.

I have templating in the info.md file on one of my plugins, and I’m not seeing the same issue there, so could this be an issue which just affects integrations, or maybe even just just the HACS integration in particular?

Top Results From Across the Web

Manually creating a single issue template for your repository

github/ISSUE_TEMPLATE/issue_template.md . You can also store multiple issue templates in an ISSUE_TEMPLATE subdirectory within the root or docs/ directories.

A GitHub Issue Template for Your Projects - Embedded Artistry

md ). I've chosen to create a Markdown template so you can use features like Markdown formatting, @-mentions, and task lists. Once GitHub ......

Only one issue template is displayed on GitHub though ...

We have created multiple issue templates in the .github/ISSUE_TEMPLATE/ subdirectory: _bug_report.md , _feature_request.md and _question.md ...

Making Most Out of GitHub Templates - Daily.dev

Unlike issue templates, you have to create PR templates manually. To create multiple PRs, store the .md files inside a PULL_REQUEST_TEMPLATE ...

GitLab Issue Templates - Save time and ... - Gary Bell

Issue templates are written in markdown. They exist as .md files within your project repository. Create a template in the .gitlab/ ...