-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[DISCREPANCY] Indentation in the generated markdown file #8
Comments
To add more info, instead of injecting an |
@revati-naik Thank you for the report. |
@revati-naik I can add configuration options for the default list marker and indentation level. |
This would be a much appreciated enhancement @liran-funaro -- I am running into a similar issue where I am using the output of sphinx-markdown-builder as the input for mkdocs, and my lists break entirely because of this. |
@ahjota @revati-naik I added a config parameter "markdown_bullet". You can set it to any value you want. You can install the latest commit and see if it solves this issue for you. pip uninstall sphinx-markdown-builder
pip install git+https://github.com/liran-funaro/sphinx-markdown-builder.git@main |
Describe the discrepancy
A clear and concise description of the discrepancy.
The markdown file that is generated from a given .rst file does not work for me. For example, in the markdown file, I need the indentation to be 4 spaces and what I see in the markdown is two spaces. I see
*
at the start of the line but I need a-
. These are with respect to creating an index file.To Reproduce
Steps to reproduce the behavior:
Sample '.rst' index file
doc1
doc2
Expected output
A clear and concise description of the expected output.
Current output
A clear and concise description of the expected output.
Environment (please complete the following information):
Additional context
Add any other context about the discrepancy here.
The indentation is right now only 2 spaces, I need 4. Any way to change this? Also the child_doc1 and child_doc2 are not listed.
The text was updated successfully, but these errors were encountered: