Closed jdimmerman closed 3 weeks ago
@jdimmerman thank you for posting these details.
we'll try to reproduce your current linters config in a week or so, as we are taking some time off after this brisk tooling run to get some cool new basic commands for you to use on Evidence dev projects in vscode.
Your notes are stellar and we might have a solution for that markdown related linting problem later on.
Also, good to see that you are testing it with mdx
too. It's one of the well designed and supported markdown extensions ecosystems out there.
@RandomFractals that sounds great and I get that... I hope that you have a good and relaxing week and thanks!
Hey @RandomFractals - Just following up here, thanks!
@hughess
And @ItsMeBrianD - I'm guessing this should be in the main evidence repo? WDYT?
Yeah I think the main repo is the best place to address this
Steps To Reproduce
With my eslint configuration, which includes prettier, the eslint rules themselves are firing on the javascript but the prettier rules are not.
Some notes
npx eslint .
) and via the VSCode eslint extensionmdx
eslint plugin so that frontmatter didn't cause linting failures, but even without this plugin I was unable to get prettier rules to fireI've posted my eslint config below and then these screenshots to illustrate the issue. Notice
eslint/no-undef
andprettier/prettier
rules are firingeslint/no-undef
rule is firingEnvironment
node -v
): 19.7npm -v
): 9.5.eslintrc.cjs
.prettierrc
Expected Behavior
Eslint and prettier rules fire in .md files, similar to .svelte files
Actual Behaviour
Only Eslint rules fire in the .md files and prettier rules do not.
Workarounds
Don't use prettier in .md files.