Incorrect file name for markdown commands

[Turtle-In-Space]

Bashly Version

Latest Ruby Gem

Description

When creating markdown files with render :markdown, the links in the index.md file does not contain the extension ".md". Resulting in them not being valid links on github for example. The markdown files created has the extension.

Contents of bashly.yml

name: download
help: Sample minimal application without commands
version: 0.1.0

commands: 
  - name: upload
  - name: download

Reproduction Steps

bashly init --minimal  
# create atleast 2 commands in bashly.yml
bashly generate
bashly render :markdown

Actual Behavior

file docs/index.md

download

Sample minimal application without commands

Attributes
Version:	0.1.0

Usage

download COMMAND

Commands

• upload -
• download -

Expected Behavior

file docs/index.md

download

Sample minimal application without commands

Attributes
Version:	0.1.0

Usage

download COMMAND

Commands

• upload -
• download -

(added ".md" at the end of both files.)

[DannyBen]

This is by design. Most markdown servers and static renderers do not need this .md extension. It is like having URLs with .html extension.

However, I can see the use case of making a github-compatible markdown renderer.

For the time being, you can probably achieve this by using custom render templates.

[Turtle-In-Space]

Ah okay, thank you for the clarification!

[DannyBen]

I am checking the possibility of allowing to render with extensions.
In the meantime, if you need help with the custom template, I can assist.

[Turtle-In-Space]

Thank you very much but that wont be necessary, I got the template working :)

[DannyBen]

I have added a new render template, called :markdown_github - which will add the .md extension, as well as name the main file README.md instead of index.md. 👉 #640.

Are there any other changes you believe this template should have?

[Turtle-In-Space]

No not that I can think of. This seems like a great solution!

[DannyBen]

Excellent. I will merge it then.

[DannyBen]

Released in v1.3.1, thanks for opening this issue.