Updated readme to document resharper support

Author: xentropic-dev

README.md

@@ -33,7 +33,6 @@ git clone \
 - If using [vim-plug][3]: `Plug 'mfussenegger/nvim-lint'`
 - If using [packer.nvim][4]: `use 'mfussenegger/nvim-lint'`
 
-
 ## Usage
 
 Configure the linters you want to run per file type. For example:
@@ -52,7 +51,6 @@ will be picked up in that buffer. This is useful for linters like
 [actionlint][actionlint] in combination with `vim.filetype` patterns like
 `[".*/.github/workflows/.*%.yml"] = "yaml.ghaction",`
 
-
 Then setup a `autocmd` to trigger linting. For example:
 
 ```vimL
@@ -80,11 +78,9 @@ Some linters require a file to be saved to disk, others support linting `stdin`
 input. For such linters you could also define a more aggressive `autocmd`, for
 example on the `InsertLeave` or `TextChanged` events.
 
-
 If you want to customize how the diagnostics are displayed, read `:help
 vim.diagnostic.config`.
 
-
 ## Available Linters
 
 There is a generic linter called `compiler` that uses the `makeprg` and
@@ -195,6 +191,7 @@ Other dedicated linters that are built-in are:
 | [quick-lint-js][quick-lint-js]         | `quick-lint-js`        |
 | [redocly][redocly]                     | `redolcy`              |
 | [regal][regal]                         | `regal`                |
+| [resharper][resharper]                 | `resharper`            |
 | [Revive][14]                           | `revive`               |
 | [rflint][rflint]                       | `rflint`               |
 | [robocop][robocop]                     | `robocop`              |
@@ -249,7 +246,6 @@ Other dedicated linters that are built-in are:
 You can register custom linters by adding them to the `linters` table, but
 please consider contributing a linter if it is missing.
 
-
 ```lua
 require('lint').linters.your_linter_name = {
   cmd = 'linter_cmd',
@@ -273,7 +269,6 @@ generate some of the properties.
 - `bufnr`
 - `linter_cwd`
 
-
 The `output` is the output generated by the linter command.
 The function must return a list of diagnostics as specified in `:help
 diagnostic-structure`.
@@ -300,7 +295,6 @@ parser = require('lint.parser').from_errorformat(errorformat)
 
 The function takes two arguments: `errorformat` and `skeleton` (optional).
 
-
 ### from_pattern
 
 Creates a parser function from a pattern.
@@ -319,7 +313,6 @@ The function allows to parse the linter's output using a pattern which can be ei
   from the linter output and must return a string array with the matches. The
   array should be empty if there was no match.
 
-
 ### groups
 
 The groups specify the result format of the pattern.
@@ -348,7 +341,7 @@ The captures in the pattern correspond to the group at the same position.
 
 A mapping from severity codes to diagnostic codes
 
-``` lua
+```lua
 default_severity = {
 ['error'] = vim.diagnostic.severity.ERROR,
 ['warning'] = vim.diagnostic.severity.WARN,
@@ -374,7 +367,6 @@ Additional options
 - `end_col_offset`: offset added to `end_col`. Defaults to `-1`, assuming
   that the end-column position is exclusive.
 
-
 ## Customize built-in linters
 
 You can import a linter and modify its properties. An example:
@@ -400,7 +392,6 @@ lint.linters.cspell = require("lint.util").wrap(lint.linters.cspell, function(di
 end)
 ```
 
-
 ## Display configuration
 
 See `:help vim.diagnostic.config`.
@@ -413,7 +404,6 @@ local ns = require("lint").get_namespace("my_linter_name")
 vim.diagnostic.config({ virtual_text = true }, ns)
 ```
 
-
 ## Get the current running linters for your buffer
 
 You can see which linters are running with `require("lint").get_running()`.
@@ -429,17 +419,14 @@ local lint_progress = function()
 end
 ```
 
-
 ## Alternatives
 
 - [Ale][1]
 - [efm-langserver][6]
 - [diagnostic-languageserver][7]
 
-
 ## Development ☢️
 
-
 ### Run tests
 
 Running tests requires [busted][busted].
@@ -607,3 +594,4 @@ busted tests/
 [twig-cs-fixer]: https://github.com/VincentLanglet/Twig-CS-Fixer
 [fortitude]: https://github.com/PlasmaFAIR/fortitude
 [redocly]: https://redocly.com/docs/cli/commands/lint
+[resharper]: https://www.jetbrains.com/help/resharper/ReSharper_Command_Line_Tools.html