John Kane

Released as part of `v0.8.4`

> Released as part of `v0.8.4` Thanks for the report, this is a bug in our release scripts (the extra syntax file wasn't being copied). I have put [together a...

> > Released as part of `v0.8.4` > > Thanks for the report, this is a bug in our release scripts (the extra syntax file wasn't being copied). I have...

Thanks for the reproduction repo. This is likely that our usedef analysis is not taking into account named parameters in invocations. That entire area is being rebuilt to leverage [slang](https://github.com/NomicFoundation/slang),...

Those are great catches, thanks! The syntax highlighting in vscode is handled by its own built-in system based on textmate grammars. You can find the file here: https://github.com/NomicFoundation/hardhat-vscode/blob/98a39356645596e4725a37ef7cd52708e399e4aa/client/syntaxes/solidity.json#L3

> I have the same problem. The tokens exist in your syntax file, they just not being recognized by the editor for some reason... > > for me the tokens...

> [@kanej](https://github.com/kanej) there's no specific steps.. just create a new .sol file inside an empty folder and the bugs are there ( import curly braces, constructor parenthesis etc ) >...

With that code, I don't get the syntax highlighting oddity:  @antico5 is it possible this could come about due to an error or inconsistency with Semantic Highlightling? @moneyDev1111 can...

Thanks @moneyDev1111, can you check if the Solidity extension is printing any errors: 

I have not been able to reproduce this error when navigating within the vscode extension against the protokol template repo. Which version of the language server is being used by...