Foliantcontrib.includes

Latest version: v1.1.18

Safety actively analyzes 685670 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 4 of 5

1.0.11

- Take into account the results of work of preprocessors that may be applied before includes within a single Foliant project. Rewrite the currently processed Markdown file path with the path of corresponding file that is located inside the project source directory *only* if the currently processed Markdown file is located inside the temporary working directory *and* the included file is located outside the temporary working directory. Keep all paths unchanged in all other cases.

1.0.10

- Do not rewrite source Markdown file if an error occurs.

1.0.9

- Don’t crash on failed repo sync (i.e. when you’re offline).

1.0.8

- Require at least one space after hashes in the beginning of each heading.
- Add `inline` option to the `<include>` tag.
- Fix the bug: do not ignore empty lines after headings when using `sethead`.
- Fix the bug: allow to use less than 3 characters in the heading content.
- Do not mark as headings the strings that contain more than 6 leading hashes. If shifted heading level is more than 6, mark the heading content as bold paragraph text, not as heading.

1.0.7

- Fix paths resolving in case of recursive processing of include statements.
- Allow revision markers in repo aliases.

1.0.6

- Fix logging in file search method.
- Fix top heading level calculation.

Page 4 of 5

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.