Open ryanjwessel opened 4 years ago
Actually, I realized once I added proseWrap: 'always'
to my .prettierrc.json
, it formatted the line-length issues correctly. But, I am still getting these errors:
26:69 error Emphasis should use `*` as a marker (emphasis-marker) md/remark
38:20 error Missing new line after list item (list-item-spacing) md/remark
39:1 error Marker should be `1`, was `2` (ordered-list-marker-value) md/remark
372:1 error Use the trailing `[]` on reference links (no-shortcut-reference-link) md/remark
So I am still trying to work these out.
I've spent some more time on this, but no luck.
My end goal is that Prettier will format my Markdown files according to the configurations we've added to ESLint for this plugin. Is this possible?
This is a few years later and it seems like this eslint plugin is still one of the most popular for markdown, but I am running into the EXACT same issues as you. @ryanjwessel did you happen to ever figure this out?
Sorry @GitMurf, I don't remember finding a solution to this problem.
Hi, I am loving this library already. Linting entire Markdown files with ESLint is great, so I'm glad you put this together.
I am having trouble getting this to work as expected with Prettier though. It is not formatting my files to account for line-length.
Here is my
.prettierrc.json
:and here is my
.eslintrc.json
:and here are the dependencies from my
package.json
:For reference, I am using VSCode, but I can't get this working from the CLI either. I would appreciate any help you can provide!