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
Brilliant tool, thanks for building and sharing it.
I found our repository AFM-SPM/TopoStats:main failed on a few things, one of which was using a [PC180](https://learn.scientific-python.org/development/guides/style#PC180): Uses a markdown formatter.
We do use prettier in our .pre-commit-config.yaml but via pre-commit/mirrors-prettier which I'll change to rbubley/mirrors-prettier.
However, we also lint our Markdown with markdownlint-cli2 and I was wondering if that qualified as a valid Markdown linter to have in place and if so whether it could be added.
The text was updated successfully, but these errors were encountered:
Sure, I think it would be fine if you want it in the list. Though I think that's a linter, rather than a formatter, but if someone has that, it's probably not helpful to ask them to add a formatter too?
Brilliant tool, thanks for building and sharing it.
I found our repository AFM-SPM/TopoStats:main failed on a few things, one of which was using a
[PC180](https://learn.scientific-python.org/development/guides/style#PC180): Uses a markdown formatter
.We do use
prettier
in our.pre-commit-config.yaml
but via pre-commit/mirrors-prettier which I'll change torbubley/mirrors-prettier
.However, we also lint our Markdown with markdownlint-cli2 and I was wondering if that qualified as a valid Markdown linter to have in place and if so whether it could be added.
The text was updated successfully, but these errors were encountered: