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
On Windows if you run yarn lint-staged on a commit that contains a link like [my link](./filter.md) it will be converted to a path like [my link](\docs\apis\core\reportbuilder\filtering.md)
I'm guessing it should probably be just left alone, since changing it to [my link](/docs/apis/core/reportbuilder/filtering.md) causes it's own issues.
It looks as though it is markdownlint-cli2 --fix that is doing this, probably via the renamedLinks Identify and fix renamed links rule which appears to be one we have added and not a part of the core markdownlint-cli2 ruleset.
It looks as though we are using the node.js path library in a way that makes the links work dependant on the OS, we can force it to always use more Linux like links by changing from just path to path.posix
What is the issue that you're experiencing?
On Windows if you run
yarn lint-staged
on a commit that contains a link like[my link](./filter.md)
it will be converted to a path like[my link](\docs\apis\core\reportbuilder\filtering.md)
I'm guessing it should probably be just left alone, since changing it to
[my link](/docs/apis/core/reportbuilder/filtering.md)
causes it's own issues.Are you able to provide a patch for this?
Yes, in pull request #1198
The text was updated successfully, but these errors were encountered: