mgzenitech

> Thanks for sharing. The issue title refers to deleting items, but the snippets and description refer to commenting things out. Are you able to reproduce the described behavior when...

> interesting idea. personally i never use `__all__` and instead just rely on prefixing symbols with `_` to mark them as private > > i think both ways are pretty...

I have one more idea that could be very universal... what about just adding setting to ensure that we have mandatory symbols in each module? In my case I'd add...

> I don't get the need, passing a stdin + filename, so here you are somehow asking for another way to pass a file. > > Why not, maybe, but...

yeah, once someone adds this I'll update config for any-lint too. Right now only onsave event supported: https://github.com/tamayika/vscode-any-lint/blob/main/examples/dotenv-linter.jsonc

> > The idiomatic way of accepting stdin instead of a file in a cli should be using - as a filename. > > That's definitely a well established pattern....

> > Will you also accept file name argument when doing stdin? Because otherwise you will not have enough information to display in error messages. And I think without file...

> > if we pipe the content without known file what will be in `${file}`? > > Any-lint needs error messages to contain path to the file even when passed...

> Yes, it is possible to make `filename` placeholder optional in `format` setting. cool, so if @tamayika can patch the extension to get the filename automatically then this only needs...

> @mgzenitech I have supported it in `0.4.1`. Also, I added `extraArgs` to support `change` and `save` event in one configuration. Please see [eslint example](https://github.com/tamayika/vscode-any-lint/blob/main/examples/eslint.jsonc) How to configure it to...