eslint-plugin-functional VS safeql

It recommend using https://github.com/eslint-functional/eslint-plugin-functional to force readonly on all properties.

Here's one the PRs that this issue happens with: https://github.com/eslint-functional/eslint-plugin-functional/pull/397

Here's the CI log link.

Also add this no-mutation ESLint rule as extra protection https://github.com/jonaskello/eslint-plugin-functional/blob/master/docs/rules/immutable-data.md

I just use https://github.com/jonaskello/eslint-plugin-functional

Cool. How does this compare to SafeQL, PgTyped, and Postgres language server ?

Anyways, an alternative if you're interested in using raw sql for max efficiency is an interesting project called SafeQLwhich treats inline queries as something to be linted. The only issue with that is if you develop on Windows, it doesn't work unless you're using WSL.

If you want to just write raw/valid SQL safely - SafeQL is great, one major issue though is that it doesn't work on Windows (you can hack it with WSL).

SafeQL I think could replace a lot of ORM code, the only issue is it doesn't support Windows if you need that.

If there was a tool that plugs into your linter (ESLint) and helps you find and fix these issues, would you use it? Luckily, I just wrote one - SafeQL.

Last week, I wrote a post about a plugin (that lints your SQL queries) called SafeQL. While doing so, I wrote this line:

Be sure to follow this issue if you're interested - https://github.com/ts-safeql/safeql/issues/14

SafeQL is currently in its very early stages, but we can make it better with the community's help! If you have any ideas/improvements/bugs to share, be sure to file an issue in our GitHub repository.