Andrew

Would like every section save the InfluxDB output plugin removed from the stock config, for brevity. Other options can be described in documentation. On Fri, May 9, 2025 at 5:28...

> Most packages are unscoped, and the risks are actually higher for scoped packages than unscoped ones, because of frequent use of internal scopes without reserving the corresponding public scope....

Request that we deprecate unscoped packages. That's a low impact change with manageable risk of breaking behavior. We can establish an expiration date, a year or two in advance, for...

Indeed, this is a breaking change. It won't happen overnight. But the community can gradually migrate to proper scoped packages in time. Published a basic linter to assist with identifying...

Update: Not all of the deep, CSS based options are demonstrated in the default configuration file. Based on themes (which tend not to support overriding style settings), we find some...

Go 1.23.0 has now been released as well. https://go.dev/doc/go1.23

Yarn constraints sounds like the ideal way to implement this, for JS projects that use Yarn. Took the liberty of writing a basic linter (Yarn and pure NPM). https://github.com/mcandre/periscope

nano is more minimalist and installed on even more platforms than vi. My own preferred editor in terminals is Vi(m). But for portability nano is more ideal.

> What is wrong with func f() (x, y float64) ? That line is fine, but there are some contexts, and many Go programmers, who wish to prohibit named returns....

Nah, that's a good point about the existing rule conflicting with a more flexible rule. I also enable all possible checks. Time is too valuable individually opting into every single...