eslint warnings don't fail the pre-commit hook or CI

[jacobtylerwalls]

eslint warnings (vs. errors) don't fail the build or CI. I think it would be better to either silence messages we don't care about or elevate them to errors, otherwise they'll just accumulate.

Our eslint config pulls in some rules configured at the warning level, here:

arches-lingo/eslint.config.mjs

Line 11 in e8f9a00

...pluginVue.configs['flat/recommended'],

If you elevate one of them to an error, you get a bunch of fixes generated by the pre-commit hook. (I've also tinkered with this particular option following this instruction for prettier compat.)

diff --git a/eslint.config.mjs b/eslint.config.mjs
index ab51240..130a4ee 100644
--- a/eslint.config.mjs
+++ b/eslint.config.mjs
@@ -38,6 +38,9 @@ export default [
         },
         "rules": {
             "semi": ["error", "always"],
+            "vue/html-self-closing": [
+                "error", { "html": { "void": "any" } }
+            ],
         },
     },
 ];

I'll PR the fixes so you can see it.

---

But we already have some other warnings in the build if you npm run eslint:check:

/Users/.../prj/arches-lingo/arches_lingo/src/arches_lingo/components/generic/resource-instance-relationships/ResourceInstanceRelationshipsEditor.vue
  11:9  warning  Prop 'val' requires default value to be set  vue/require-default-prop

✖ 1 problem (0 errors, 1 warning)

☝️ seems like something would have been nice to address at the source

/cc @chrabyrd