diff --git a/index.xhtml b/index.xhtml index d59f7b8..3d2511e 100644 --- a/index.xhtml +++ b/index.xhtml @@ -33,7 +33,7 @@
Table of Contents
Table of Contents
If you noticed a bug caused by nvf then please consider reporting it over the issue tracker.
Bugfixes, feature additions and upstreamed changes from your local configurations are always welcome in the the pull requests tab.
diff --git a/plugins.html b/plugins.html index d241b76..b360b67 100644 --- a/plugins.html +++ b/plugins.html @@ -24,9 +24,12 @@At times, certain plugins refuse to play nicely. Be it as a result of generating +
Table of Contents
At times, certain plugins refuse to play nicely. Be it as a result of generating lua from Nix, or the state of packaging. This page shall list any plugins that -are known to misbehave, and potential workarounds.
+are known to misbehave, and potential workarounds.Table of Contents
When working with NodeJS, everything works as expected, but some projects have settings that can fool nvf.
If this plugin or similar is included, you might get a situation where your eslint configuration diagnoses your formatting according to its own config (usually .eslintrc.js
).
The issue there is your formatting is made via prettierd.
This results in auto-formating relying on your prettier config, while your eslint config diagnoses formatting which it’s not supposed to)
In the end, you get discrepancies between what your editor does and what it wants.
Solutions are:
Don’t add a formatting config to eslint, and separate prettier and eslint.
PR this repo to add an ESLint formatter and configure nvf to use it.