neoclide / coc-json Goto Github PK

View Code? Open in Web Editor NEW

231.0 231.0 21.0 453 KB

Json language extension for coc.nvim

TypeScript 98.23% JavaScript 1.77%

coc json neovim vim

coc-json's Introduction

Neoclide is a rework of Nyaovim, the reason is I want it have best user experience.

Neoclide is an editor built with web technologies while emebed with neovim.

Neoclide is in early development, which means it could break easily, and you should not take it seriously.

Since I use Mac only, something could break on other platform, I need your help!

What have done

Global session save and restore
Fixed copy/paste behaviour
Fixed drag and click position calculate
Fixed trigger of VimLeave event
Background transparent support
Improved input method support
Improved cursor support
Accessable editor state object
Automatic resize handler, no screen blink

How to use

Since it's in early age, no prebuild currently avaiable, you have to use it from souce code.

Clone this repository
Run following commands to install dependencies and build code
```
npm run dep
npm run build
```
To start the app, use:
```
npm run app
```

LICENSE

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

coc-json's People

Contributors

Stargazers

Watchers

coc-json's Issues

bug: reports `incorrect type. Expected "object"`

A json with a top level array or string throws an error

[json] [W] Incorrect type. Expected "object".

This seems to be unique to this project as opening the same file in vscode does not have this problem.

here is some examples of files that are valid json but coc-json is throwing an error:

"foo.json"

"foo"

"bar.json"

["bar"]

the output of CocInfo

## versions

vim version: NVIM v0.3.3
node version: v8.12.0
coc.nvim version: 0.0.59
term: iTerm.app
platform: darwin

## Error messages

## Output channel: prettier

## Output channel: snippets

## Output channel: highlight
[Info  - 13:57:25] Highlight server running in node v8.12.0

Here is my coc extensions/package.json

{
  "dependencies": {
    "coc-css": "^1.0.7",
    "coc-dictionary": "^1.2.0",
    "coc-emmet": "^1.0.9",
    "coc-emoji": "^1.2.0",
    "coc-eslint": "^1.1.0",
    "coc-highlight": "^1.0.5",
    "coc-html": "^1.0.7",
    "coc-jest": "^1.0.1",
    "coc-json": "^1.0.12",
    "coc-omni": "^1.2.0",
    "coc-prettier": "^1.1.0",
    "coc-snippets": "^2.0.2",
    "coc-stylelint": "^1.0.8",
    "coc-tag": "^1.2.0",
    "coc-tsserver": "^1.1.30",
    "coc-vetur": "^1.1.0",
    "coc-word": "^1.2.0",
    "coc-yaml": "^1.0.0",
    "coc-yank": "^1.0.2"
  }
}

Schema support of `contributes` field for package.json

VSCode support that.

tsconfig.json [json 521] [e] Comments are not permitted in JSON.

I suggest adding the ability to configure exceptions in the rules for some files.

chrome extention manifest 3 not supported

It seems to say manifest version 2 is the latest but right now it is 3.

Formatting does not work correctly

I created a simple json file with the following content:

[
    {
    "link": {
        "bashrc": "~/.bashrc"
        }
    }
]

Then I tried to use coc-json to format it. The result is as follows:

[
    {
        "link": {
            "bashrc": "~/.bashrc"
        }
    }
]
    "link": {
        "bashrc": "~/.bashrc"
        }
    }
]

The formatted document has some part of text dupliated and has an extra right bracket.

Disable diagnostics

How can I disable diagnostics?

Support scoped configurations

Based on this comment, coc-json does not yet support scoped configurations.

Here is an example, copied below.

{
    "[c][cpp]": {
        "semanticTokens.enable": true
    }
}

coc-json says "Property [c][cpp] is not allowed. (json)" on line 2.

current version

1.6.1

Add schema for `compile_commands.json`

clang-based tools rely on a compilation database to work correctly. Such a file is named compile_commands.json. When a valid compile_commands.json is opened in vim, coc-json reports a "fake" warning message

[json] [W] Incorrect type. Expected "object".

and highlights the whole compilation database. This can be quite annoying as a compilation database can be quite large, and this lint highlight causes vim to freeze up a bit when closing the file.

This issue is brought up in #9 but closed without actually being fixed. One can see that the current catalog.json file still does not contain the schema for compilation database, which was added in the schemastore in SchemaStore/schemastore#934.

EDIT:
I added the following schema to my coc-settings.json to add support for compile_commands.json:

"json.schemas": [
     {
       "fileMatch": ["compile_commands.json"],
       "url": "http://json.schemastore.org/compile-commands"
    }
],

However, I still get the same warning message. After some debugging, I found that this is because compile_commands.json matches two schemas simultaneously. One is http://json.schemastore.org/compile-commands (which matches to compile_commands.json), and the other one is http://json.schemastore.org/commands (which matches to commands.json). commands.json is supposed to contain json objects rather than arrays, hence the message [json] [W] Incorrect type. Expected "object".

I don't know if this is only an issue for coc-json, or it also applies to other editor plugins such as vscode-json-languageservice. However, this does seem like a bug for me.

coc-json does not provide any diagnostics

npm list vscode-json-languageserver ─╯
[email protected] /home/harvey/.config/coc/extensions/node_modules/coc-json
└── (empty)

It does not format Json when saving!!

Hello, when saving the file Formatting doesn't happen, how should I format Json?

Get coc-json work in SpaceVim/neovim

Hi there,

I try to get coc-json with a custom coc-settings.json working. The default schema for coc-settings.json itself works like a charm, but any custom added schemas don't.

I use SpaceVim on top of neovim (0.6.1). My general config look like:


call coc#config('coc.preferences', {
                        \ "autoTrigger": "always",
                        \ "maxCompleteItemCount": 10,
                        \ "codeLens.enable": 1,
                        \ "diagnostic.virtualText": 1,
                        \})

let s:coc_extensions = [
                        \ 'coc-json',
                        \]

for extension in s:coc_extensions
        call coc#add_extension(extension)
endfor```

And my _coc-settings.json_ looks like:

{
"json.schemas": [
{
"fileMatch": [
"gitlab-ci.yml"
],
"url": "https://gitlab.com/gitlab-org/gitlab/-/raw/master/app/assets/javascripts/editor/schema/ci.json"
}
]
}


But autocompletion doesn't work at all. I find out that coc-json is not enabled by default, so I do this by `CocList extensions` and try to run `CocCommand json.retryResolveSchema`.

I'm pretty new to vim, so I'm sure I'm missing something 😬 

Thanks in advance,
Hauke

Unable to disable schema

I have a file named app.json, which is getting incorrectly detected as an "Expo SDK" file.
Is there a way to disable that schema from the builtin catalog?

I tried to override it through the json.schemas setting, but to no avail:

"json.schemas": [
  { "fileMatch": ["app.json"], "url": "" }
]

Incorrect type. Expected "array". in manifest.json

For some reason, I'm getting a weird error when opening a Chrome extension manifest file:

Incorrect type. Expected "array".

What is causing this?

date-time validation

Hi,
thanks for this awesome coc extension, I use it often. I stumbled upon a problem with date-time validation.
This is my schema:

{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "type": "object",
  "properties": {
    "date": {
      "type": "string",
      "format": "date-time"
    }
  }
}

This is my JSON:

{
  "date": "020-12-23T18:25:43.511Z"
}

The year is missing the first digit and coc-json does not report any errors. Actually no errors are detected, it seems like it ignores the validation. When I set the format to email, all erroneous mail addresses are reported, so the format validation is working.
Here is how it should behave: https://www.jsonschemavalidator.net/s/AjNuDoH9

Is that a known issue?

Extension-related items doesn't exist in Autocompletion list (version from 1.3.0)

Desc

:CocConfig open the coc-settings.json
I have installed some coc extensions like coc-prettier, coc-eslint, but I can't get those related items in the autocompletion popup list while I'm tying.
When I install [email protected], everything is fine, but version from 1.30 has this issue.

Env

neovim: v0.44
coc-json: ^1.3.0

Enum Descriptions not being showed in the editor when key is `title`

Hello !
Recently, maintainers of the protoc-gen-jsonschema plugin maintainers have added support for generating descriptions out of the comments for the enum type in a Protobuf file.
These descriptions are stored as "title":"My description" in the generated json schema (draft-06), but they are not showing up my editor.
I guess that coc only triggers on the "description": "my desc" key value ? If yes, is there any way to fix this or give an option ?

I would immmmmmeeeeeensely appreciate as I rely on having enum descriptions available when editing a particular schema !
Thanks in advance for any news or help !

how to format json with CocAction('format')?

Feature Suggestion: Make trailingComma ignorable by a configuration variable

Trailing commas have grown quite popular at this point. This warning could be toggleable.

Property 'schemes' does not exist on type 'Extensions'.

Hi,

Yesterday compilation was fine but not this morning. I guess is linked to the commit 244bb7f

$ tsc -p tsconfig.json
src/index.ts:179:24 - error TS2339: Property 'schemes' does not exist on type 'Extensions'.

179         if (extensions.schemes) Object.assign(schema.properties, extensions.schemes)
                           ~~~~~~~

src/index.ts:179:77 - error TS2339: Property 'schemes' does not exist on type 'Extensions'.

179         if (extensions.schemes) Object.assign(schema.properties, extensions.schemes)
                                                                                ~~~~~~~


Found 2 errors.

error Command failed with exit code 2.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
ERROR: "build" exited with 2.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

Missing property "pages"

coc-json seems to be reporting a warning on app.json that I don't know where it is coming from.

I verified that coc-json is reporting this warning because after disabling coc-json, I don't get the warning. See screenshots 1 & 2 below.

I have checked the schemastore repository looking for any app.json in fileMatch, but didn't find any (ref).

Reproduction Steps

In neovim:

:e app.json
go into insert mode i, type {}, go back to normal mode ESC, and save :w
warning shows up

Screenshot 1

Screenshot 2

json5 support

When I set the filetype of my buffer to [json5] (either vim or nvim), then I don't get intellisense and the other goodies.

Is it possible to make this package also support json5 or we would have to create a dedicated coc-json5 plugin?

Add a command like yaml.selectSchema

It would be nice to be able to select a schema store schema interactively.

Getting strange warnings after upgrading to 1.7.0

At 1.6.1 I'm seeing the following warnings in my coc-settings.json:

I believe these are valid.

But after upgrading to 1.7.0, I'm getting this warning:

Configuration property may not work as folder configuration (json)

Any idea why this is happening?

Autocompletion does not show up

Using nvim v0.4.4 with coc-json and coc-tsserver installed. When I open :CocConfig and type around the JSON file and try to use autocomplete no settings appear. How can I troubleshoot the autocomplete issue?

Schema Error for Windows Terminal Settings

Hello All,

I'm trying to use coc.json to edit my settings.json for the windows terminal.

Most everything works fine, only it throws a "schemas are not fully supported yet" error (pictured below)

Do we know when this will be supported?

Thanks for your wonderful plugin, I appreciate your time and expertise.

No schema completions for `tsconfig.json`

I've been trying to get completions for tsconfig.json working, and have debugged as far as I can.

The README suggests that with default settings I should get support for all the schemas listed at https://raw.githubusercontent.com/SchemaStore/schemastore/master/src/api/json/catalog.json.

But when debugging with json.trace.server: "verbose" I see this:

[Trace - 7:07:56 pm] Sending notification 'json/schemaAssociations'.
Params: [
    [
        {
            "fileMatch": [
                "coc-settings.json"
            ],
            "uri": "vscode://settings"
        },
        {
            "fileMatch": [
                "package.json"
            ],
            "uri": "vscode://schemas/vscode-extensions"
        },
        {
            "fileMatch": [
                "/*.html-data.json"
            ],
            "uri": "https://raw.githubusercontent.com/microsoft/vscode-html-languageservice/master/docs/customData.schema.json"
        },
        {
            "fileMatch": [
                "/package.json"
            ],
            "uri": "file:///home/ben/.config/coc/extensions/node_modules/coc-html/schemas/package.schema.json"
        },
        {
            "fileMatch": [
                "/.prettierrc"
            ],
            "uri": "http://json.schemastore.org/prettierrc"
        },
        {
            "fileMatch": [
                "/.prettierrc.json"
            ],
            "uri": "http://json.schemastore.org/prettierrc"
        },
        {
            "fileMatch": [
                "/package.json"
            ],
            "uri": "file:///home/ben/.config/coc/extensions/node_modules/coc-prettier/package-json-schema.json"
        },
        {
            "fileMatch": [
                "/pyrightconfig.json"
            ],
            "uri": "file:///home/ben/.config/coc/extensions/node_modules/coc-pyright/schemas/pyrightconfig.schema.json"
        }
    ]
]

Seems to suggest they're either not being used or overridden somewhere.

How can I debug where these settings are coming from?

Setting `ft=jsonc` allows comments but unsets syntax highlighting

While filetype is json (ft=json), syntax highlighting works, but errors about comments are shown. Setting ft=jsonc allows comments but unsets syntax highlighting.

Property is not allowed in coc-settings.json

I've just installed coc-json in my vim setup and i get [json] [W] Property explorer is not allowed. on some words in the local coc-settings.json file.

What happens

Some terms like "explorer", "yaml" and "json" in coc-settings.json trigger Property explorer is not allowed.

What should happen

Words like "explorer", "yaml" and "json" should be valid.

Extra notes

These keywords refer to coc modules installed using :CocInstall coc-yaml coc-json coc-explorer.

Format provider not found for file

cloud not format json file when saving it. error message from coc log:

Format provider not found for file

Allowing comments example

In the README we have:

How to suppress error [json 521] [e] Comments are not permitted in JSON?
You can configure your vim to make that file with jsonc filetype to allow comment.

Can I please have an example of this configuration?

Many thanks for this awesome project :)

coc-json deactivates coc-highlight color highlighting

After installing coc-json, color highlighting provided by coc-highlight stops working. I have set coc-settings.json to "colors.filetypes": [*] and confirmed that coc-highlight works on my vim install. Adding ".json" to the file types did not resolve the issue.

Every .json file reports "Parsing error..."

Reproduction steps:

open vim
:CocInstall coc-json
edit JSON file like this one

{
	"name": "a",
	"version": "b"
}

The claim is "Missing semicolon." on the second quote after "name.

What should I try next? I am happy try debugging. 🙂

Attempting :CocList services says: json [running] json, jsonc

My npm --version is 7.21.0 with NodeJS v16.8.0 and vim --version says:

VIM - Vi IMproved 8.2 (2019 Dec 12, compiled Aug 15 2021 13:04:41)
macOS version - x86_64
Included patches: 1-3350
Compiled by Homebrew
Huge version without GUI.  Features included (+) or not (-):
+acl               +file_in_path      +mouse_urxvt       -tag_any_white
+arabic            +find_in_path      +mouse_xterm       -tcl
+autocmd           +float             +multi_byte        +termguicolors
+autochdir         +folding           +multi_lang        +terminal
-autoservername    -footer            -mzscheme          +terminfo
-balloon_eval      +fork()            +netbeans_intg     +termresponse
+balloon_eval_term +gettext           +num64             +textobjects
-browse            -hangul_input      +packages          +textprop
++builtin_terms    +iconv             +path_extra        +timers
+byte_offset       +insert_expand     +perl              +title
+channel           +ipv6              +persistent_undo   -toolbar
+cindent           +job               +popupwin          +user_commands
-clientserver      +jumplist          +postscript        +vartabs
+clipboard         +keymap            +printer           +vertsplit
+cmdline_compl     +lambda            +profile           +virtualedit
+cmdline_hist      +langmap           -python            +visual
+cmdline_info      +libcall           +python3           +visualextra
+comments          +linebreak         +quickfix          +viminfo
+conceal           +lispindent        +reltime           +vreplace
+cryptv            +listcmds          +rightleft         +wildignore
+cscope            +localmap          +ruby              +wildmenu
+cursorbind        +lua               +scrollbind        +windows
+cursorshape       +menu              +signs             +writebackup
+dialog_con        +mksession         +smartindent       -X11
+diff              +modify_fname      -sodium            -xfontset
+digraphs          +mouse             -sound             -xim
-dnd               -mouseshape        +spell             -xpm
-ebcdic            +mouse_dec         +startuptime       -xsmp
+emacs_tags        -mouse_gpm         +statusline        -xterm_clipboard
+eval              -mouse_jsbterm     -sun_workshop      -xterm_save
+ex_extra          +mouse_netterm     +syntax            
+extra_search      +mouse_sgr         +tag_binary        
-farsi             -mouse_sysmouse    -tag_old_static    
   system vimrc file: "$VIM/vimrc"
     user vimrc file: "$HOME/.vimrc"
 2nd user vimrc file: "~/.vim/vimrc"
      user exrc file: "$HOME/.exrc"
       defaults file: "$VIMRUNTIME/defaults.vim"
  fall-back for $VIM: "/usr/local/share/vim"
Compilation: clang -c -I. -Iproto -DHAVE_CONFIG_H -DMACOS_X -DMACOS_X_DARWIN -g -O2 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 
Linking: clang -L. -fstack-protector-strong -L/usr/local/lib -L/usr/local/opt/libyaml/lib -L/usr/local/opt/[email protected]/lib -L/usr/local/opt/readline/lib -L/usr/local/lib -o vim -lm -lncurses -liconv -lintl -framework AppKit -L/usr/local/opt/lua/lib -llua5.4 -mmacosx-version-min=11.3 -fstack-protector-strong -L/usr/local/lib -L/usr/local/Cellar/perl/5.34.0/lib/perl5/5.34.0/darwin-thread-multi-2level/CORE -lperl -L/usr/local/opt/[email protected]/Frameworks/Python.framework/Versions/3.9/lib/python3.9/config-3.9-darwin -lpython3.9 -framework CoreFoundation -lruby.3.0 -L/usr/local/Cellar/ruby/3.0.2/lib

Bug: wrong type of `Lua.workspace.library` in JSON schema

the key Lua.workspace.library expects an array of strings, however, coc-json complains that it is expecting an object. (Since the JSON schema is provided on this repo, I assume the bug is caused by this LSP server and not coc-json.)

At first I thought it was a problem on the side of the language server and reported the issue there: LuaLS/lua-language-server#1605

However, I noticed that with Sublime's LSP-lua the issue does not occur, so I assume the issue is with this plugin, but I am not sure.

coc-json extension doesn't seem to be doing anything

Hello. There's something funny going on with my extensions ever since I switched from using vim plug to install them to using the g:coc_global_extensions variable. Here's the relevant configuration I have right now:

if has('nvim')
  Plug 'neoclide/coc.nvim', { 'do': 'yarn install --frozen-lockfile' }
endif

" Completion: language-specific
if has('nvim')
  let g:coc_global_extensions = [ 'https://github.com/neoclide/coc-tsserver'
                              \ , 'https://github.com/neoclide/coc-json'
                              \ , 'https://github.com/neoclide/coc-java'
                              \ , 'https://github.com/neoclide/coc-snippets'
                              \ , 'https://github.com/masaeedu/coc-omnisharp'
                              \ , 'https://github.com/neoclide/coc-yaml'
                              \ , 'https://github.com/iamcco/coc-vimlsp'
                              \ ]
endif

However when I try to work with a JSON file it doesn't look like any of the features are working: https://asciinema.org/a/97pUN7wSQa6ah3PJEuqTrVOu7 (sorry about small font size, please zoom out a bit to fit to screen)

compile-commands.json is reported as incorrect type

The example I have is for a closed-source project, but I can try to help reproduce this using another project if needed. compile-commands.json is a big JSON array used for clang tooling. coc-json reports Incorrect type. Expected "object"..

What does this setting option mean?

json.execArgv add execArgv to child_process.spawn

Incorrect type. Expected "Buffer" when using 2019-09 schema

When I set "$schema" to "https://json-schema.org/draft/2019-09/schema" I get Incorrect type. Expected "Buffer" every time. Unsure what the error is complaining about. It does appear to download it.

Example file:

{
  "$schema": "https://json-schema.org/draft/2019-09/schema",
  "description": "Schema for myapp config",

  "type": "object",
  "additionalProperties": false,
  "properties": {
    "port": { "type": "integer", "minimum": 1024, "maximum": 65535 },
    "usessl": { "type": "boolean" },
  }
}

Json not getting formatted on save, but :call Cocaction('format') works.

When I save the coc-json file, it doesn't get formatted automatically.
However :call Cocaction('format') works perfectly.

Here is the my full coc-settings.json file.

{
  "codeLens.enable": true,
  "coc.preferences.formatOnSaveFiletypes": [
    "css",
    "markdown",
    "javascript",
    "js",
    "graphql",
    "html",
    "yaml",
    "json",
    "elixir",
    "python"
  ],
  "json.format.enable": true,
  "snippets.ultisnips.directories": [
    "UltiSnips",
    "~/.config/nvim/utils/snips"
  ],
  "explorer.width": 30,
  "explorer.icon.enableNerdfont": true,
  "explorer.previewAction.onHover": false,
  "explorer.keyMappings": {
    "<cr>": [
      "expandable?",
      "expand",
      "open"
    ],
    "v": "open:vsplit"
  },
  "eslint.autoFixOnSave": true,
  "eslint.filetypes": [
    "javascript",
    "javascriptreact",
    "typescript",
    "typescriptreact"
  ],
  "snippets.extends": {
    "javascriptreact": [
      "javascript"
    ],
    "typescriptreact": [
      "typescript"
    ]
  },
  "diagnostic-languageserver.filetypes": {
    "elixir": [
      "mix_credo",
      "mix_credo_compile"
    ],
    "eelixir": [
      "mix_credo",
      "mix_credo_compile"
    ]
  },
  "diagnostic-languageserver.formatFiletypes": {
    "elixir": "mix_format",
    "eelixir": "mix_format"
  }
}

support portable schema config

I am not sure if this is currently the case with jsonValidation under a project's package.json file, as I have tried, and it didn't seem to have an effect. But it would be great if we could be able to link schemas on a project-level, so references are portable.

For example

// /home/user/src/my-app/package.json
{
  "name": "my-app",
  "version": "0.0.0",
  "contributes": {
    "jsonValidation": [
      // this links to both json and schema on my project's `./assets` directory
      { "url": "assets/selectors.schema.json", "fileMatch": "assets/selectors.json" }
    ]
  }
}

With the above, validations are carried within the project directory and can be used on different environments independently of their ./.vim/coc-settings.json configuration, which wouldn't be needed.

This could also help package developers to use these package.json fields in order to run validation on CI level by reading the contributes.jsonValidation entries against the schemas defined.

Unclear explanation

"How to suppress error [json 521] [e] Comments are not permitted in JSON?

You can configure your vim to make that file with jsonc filetype to allow comment."

This might be the most unclear explanation ever... What do you mean?

Add support for `.hjson` and `.json5` types.

hjson especially is a popular format for config files, allows comments and such.

how to change indentation

I want to change indentation. But I don't now how.

Incorrect type. Expected "array" - in package.json dependencies

Dependencies should be an object (just like devDependencies, which doesn't throw an error)

How to add extra schema definitions/properties?

I want add extra schema definitions for my JSON config file, likes what coc-settings.json does. Can you help with how to do it? Thanks.

Error on activate extension coc-json

load schema error caused by protocol

warning information:

[coc.nvim] Schema error: Problems loading reference 'https://json.schemastore.org/tsconfig': Unable to load schema from 'https://json.schemastore.org/tsconfig': Request vscode/content fail
ed with message: Request failed using proxy 192.168..: Protocol "https:" not supported.
Expected "http:".

environment:

NVIM v0.5.0
the latest coc-json & coc.nvim

Another JSON file also with an empty JSON object reports no warnings:

However, when I change the name of the offending file to triox.json no warnings are reported: