You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think this project has unique features (ie. built-in globbing and direct md analysis without compilation to html) among competitors (ie. markdown-link-check) and is good enough to deserve a proper evolution path in next future.
[-e option] add support to optional .md extension (ie. for [internal page](./path/to/page) it searches also for [internal page](./path/to/page.md) or [internal page](./path/to/page/index.md)
add support to standalone links checking (ie. without [anchor](https...) or [anchor] https...)
[-c option] ignoring failing external urls based on response status codes (added to final report)
[--ignorePatternsFrom option] ignoring files by patterns taken from a file
[--noEmptyFiles option] raising error if linked files are empty
No breaking changes to the API are introduced. All existing options have the same behavior and defaults and new optional features depends on options disabled by default. Only 2), 6) and 7) are opinionated and could require some discussions. All new features have tests (but I know we can improved them further).
All changes live on feature/sparkfabrik-enhancements branch. I think all of them can met a broader interest beyond our company playbook, so I propose you to review my work and consider to accept a PR and update the npm package.
I think this project has unique features (ie. built-in globbing and direct md analysis without compilation to html) among competitors (ie. markdown-link-check) and is good enough to deserve a proper evolution path in next future.
For an internal open source project (a knowledge base written in markdown and powered by Raneto) I took the v1.0.1 (8 Jun 2021) of markdown-link-validator and made some changes to adapt it to our requirements: https://github.com/jenkin/markdown-link-validator/.
npm audit[internal page](/path/to/page.md))-qoption] add a quiet mode to report only errors if present (see issue Allow show only the errors in the report. #6)-eoption] add support to optional.mdextension (ie. for[internal page](./path/to/page)it searches also for[internal page](./path/to/page.md)or[internal page](./path/to/page/index.md)-ooption] add support to other extension checking (ie.[local asset](./path/to/image.png)(see issue Relative Image links are reported as invalid #27)[anchor](https...)or[anchor] https...)-coption] ignoring failing external urls based on response status codes (added to final report)--ignorePatternsFromoption] ignoring files by patterns taken from a file--noEmptyFilesoption] raising error if linked files are emptyNo breaking changes to the API are introduced. All existing options have the same behavior and defaults and new optional features depends on options disabled by default. Only 2), 6) and 7) are opinionated and could require some discussions. All new features have tests (but I know we can improved them further).
All changes live on feature/sparkfabrik-enhancements branch. I think all of them can met a broader interest beyond our company playbook, so I propose you to review my work and consider to accept a PR and update the npm package.