From 3c0e731fe1d7c7c75b2f563f18248ebebb4ee3fa Mon Sep 17 00:00:00 2001 From: Timur Osmanov Date: Wed, 4 Dec 2024 13:52:32 +0300 Subject: [PATCH] update: fix README.md, bump version --- README.md | 4 ++-- package.json | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 1dfba42..9e21726 100644 --- a/README.md +++ b/README.md @@ -133,9 +133,9 @@ These arguments will be make automatically using the `path` and `git-repo-name` The configuration file will list all the files specified in the `chapters` and `includes_map` sections for use as "globs". -To use the `lint all markdown files` function with the markdownlint extension for VS Code, a file will be added to the project folder `.vscode/settings.json`. +To use the `lint all markdown files` function with [the markdownlint extension for VS Code](https://marketplace.visualstudio.com/items?itemName=DavidAnson.vscode-markdownlint), a file will be added to the project folder `.vscode/settings.json`. Checking of all files will be disabled in this file, but the list of files that need to be checked will remain in the `cjs` file. -So you can use the `lint all markdown files` function in vs code, but it will check only those files that will be contained in chapters, and in includes_map.json +So you can use the `lint all markdown files` function in VS Code, but it will check only those files that will be contained in chapters, and in includes_map.json ### Examples diff --git a/package.json b/package.json index 18c7b78..9168ef7 100644 --- a/package.json +++ b/package.json @@ -1,6 +1,6 @@ { "name": "foliant-md-linter", - "version": "0.1.13", + "version": "0.1.14", "description": "CLI tool for linting Foliant markdown sources", "license": "MIT", "homepage": "https://github.com/holamgadol/foliant-md-linter",