Joosep Alviste

Hey @MuhammadSawalhy, thanks for the bug report! I added an extra rule for this exact use-case, but in general, it's a bit tricky to detect similar multi-line expressions inside `{}`...

Hey @desi-belokonska! I've also run into the same issue (and there's an issue for this already as well: #11). You're correct in the source of the issue. But I'm wondering...

Hey! There are 2 main ways that I can see how integrations might work: 1. (Preferred) The commenting plugin allows configuring a "hook" function that will be called before the...

Hey @tyru! How is the integration going on `caw.vim` side?

Hey! Just to let you know that I added a PR which does exactly this (although I only added the options for Vue files): #7.

Hey @vishalbalaji! This would be a pretty big change and I haven't really had a chance to look into it. Since it's such a small edge case, then I'm not...

I don't think it's really a problem in Treesitter or any parsers, because this is not valid jsx syntax and probably *should* result in a broken syntax tree: ```jsx (...

IIRC, the ESLint default output format does not include the severity, so I wrote my own simple output formatter: https://github.com/JoosepAlviste/dotfiles/blob/master/resources/eslint-formatter-vim.js With this new format, I could [configure EFM `lintFormats` for...

I commented on #372 but I think it makes more sense to discuss the problem here (maybe even close the other issue?) Here's my idea not requiring projectionist but just...

I'm working on this a little bit in https://github.com/JoosepAlviste/vim-test/tree/non-root-package-json but there's a small problem with the solution. Detecting the correct `package.json` and `node_modules/.bin/jest` works fine, but since the project root...