nvim-dotfiles-kitty VS Checkstyle

If you are using Kitty, you can check my configuration where I mix hologram.nvim with Telescope.

If you want to make your Neovim look like VSCode, you can check my configuration here.

Here is mine

I'm working with Java (spring boot), JS (react, svelt) and TS too, and I also try to make it look VsCode. You may want to check my dotfile Nguyen-Hoang-Nam/nvim-dotfiles-kitty, in wiki, I also add process to install language server, code formatter.

I use treesitter for syntax-highlight, Golsp, EFM for lint and code formatter (goimport, gofumpt), luasnip + friendly-snippets for snippets. My .dotfile https://github.com/Nguyen-Hoang-Nam/nvim-dotfiles

I'm trying to use Google's checkstyle. I want certain things to be an error, such as using Tabs for indentation. When I run mvn checkstyle:check with a file with a tab in the first column, it always gives a [WARN] rather than the error that I've asked for. Pom snippet: org.apache.maven.plugins maven-surefire-plugin ${maven-surefire-plugin.version} ${maven-surefire-plugin.skipUnitTests} org.apache.maven.plugins maven-checkstyle-plugin 3.1.2 checkstyle validate check google_checks.xml UTF-8 true true warning true I'm using google_checks.xml as from https://github.com/checkstyle/checkstyle/blob/master/src/main/resources/google_checks.xml. I have changed the severity for the FileTabCharacter to "error"

1. Conflicts between Spotless and Checkstyle Checkstyle is a tool for checking Java source code for compliance with code standards or a set of validation rules (best practices).

Never had anything like that though for four years my life revolved around getting PMD, checkstyle and Sonar rules to pass so my pull request would merge.

PMD, and checkstyle as well.

I’m a little out of date with Java, but I believe Checkstyle is currently popular: https://github.com/checkstyle/checkstyle

Another example can be applied to code quality itself. Most static analyzers are configurable. If you tried to set Checkstyle Google configuration to the mature project, you would probably get hundreds or even thousands of errors. You can start with just one rule. Ar first glance, it seems not so important. But after the moment when the configuration reaches the repository, you can be sure that no one else can violate this rule in the future.

Checkstyle: a tool that helps programmers write Java code that adheres to a coding standard: https://github.com/checkstyle/checkstyle

So I was there once, sharing my solution. For my current project I use the java formatter jar, but on my previous work I was using checkstyle, you can get it from here: Checkstyle. Then pass your checkstyle xml format config.