Extension reports errors everywhere, not just where they happen about bash-language-server

[skovhus]

Thanks for creating this issue. We are working on better error highlighting based on an improved version of the grammar.

We can actually improve this a lot by looking if a node isMissing or hasError.

[skovhus]

@achekulaev can you do a:
bash-language-server --version

The latest version is 1.5.2 where I don't see the mentioned syntax error.

[achekulaev]

§ bash-language-server --version
Version is 1.5.2

§ uname -a
Darwin EPUSPRIW1129 17.6.0 Darwin Kernel Version 17.6.0: Tue May  8 15:22:16 PDT 2018; root:xnu-4570.61.1~1/RELEASE_X86_64 x86_64

VisualStudio Code Version 1.26.1 (1.26.1)

Bash IDE 1.3.2

[achekulaev]

Please tell if there is anything else that will help to resolve the issue.

[skovhus]

Until we improve the parser you disable the error from showing up by setting the config parameter: bashIde.highlightParsingErrors.

With the latest version you still see the two errors reported above?

[achekulaev]

Yes for me the error is still there.

[Yanpas]

Same issue applies to

if ((${#aaa[@]} == 0)); then
fi

[Yanpas]

There are seem to be updates to grammar
tree-sitter/tree-sitter-bash#32

[skovhus]

@Yanpas 👍

Just added the upgrade of the grammar to #78

[skovhus]

@achekulaev Please reopen if this still is a problem after upgrading the bash-language-server

[Yanpas]

I face the same issues still because of complex bash grammar
(Function body range is parsed incorrectly) tree-sitter/tree-sitter-bash#35
(Error while parsing stream redirection inside dollar-parentheses) tree-sitter/tree-sitter-bash#34