azbrowse: Bug: Devcontainer linter failure - composites
Hello, I’m not actually sure this is isolated to the devcontainer, but i suspect it is based on previous conversations we’ve had.
github.com/alecthomas/chroma.Rule composite literal uses unkeyed fieldscomposites
Which appears to be caused by this structure - specifically all 19 similar structures in the same file near that area.
I suspect, the //nolint:govet comments are supposed to be preventing this type of warning, but aren’t working for some reason (I’m not familiar enough with this stuff to diagnose the issue). That said - One potential solution seems to be to simply disable that type of warning globally, but I’d assume that isn’t desirable for the project.
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 15 (14 by maintainers)
Some days you really need to just take a step back…
😔😔😔
My fix for this will be to just fix the error with a code change, since that makes for better code anyway.
they are not.
golangci-lintis clean, as is a manual vet run with the disable composites flag. It’s definitely related to the go plugins internals. my working theory is a missing flag somewhere. looking into em now.I can probably submit a quick fix for this tomorrow, stay tuned.