linting config itself wouldn't be defined there, and it would be verified in ci and such, but a setting to tell vscode which linter and extension it should use to show warnings would be.

modern languages may have their own way for configuration but they don't have a way to bind it to the list of vscode tasks and define how to run a debugger, which is the part that gets stored.

it's easy to go overboard with extension suggestions, but I don't think adding an extension for linter used, extension for formatter used, and any languages used if there's a definitive extension.

My team is split between visual studio, vscode, and I use emacs. we have config for both vs and vscode in our repos since it makes working on a new project so much nicer and means we aren't just sharing editor configs through side channels instead. it doesn't do anything to me if I have editor config for an IDE I don't use in the repo, but it makes it easier for someone new to jump in with a sort of same environment immediately