6 ms·

.vscode committed to a repository is a bit of a warning flag to me. It tells me this repo is doing some non-standard stuff that needs special IDE configuration

.vscode committed to a repository is a bit of a warning flag to me. It tells me this repo is doing some non-standard stuff that needs special IDE configuration to account for.

elashri 4y ago
or using codespaces for development
mcluck 4y ago
Or it just includes some conveniences. A lot of my projects include a .vscode folder so that anyone who uses VS Code can debug the application right away. If you want to use your own IDE or even just run everything from the terminal, it all still works.
skrtskrt 4y ago
Sufficiently complex projects are going to need some IDE config to get everything running and integrated with IDE tooling.
- AnonymousPlanet 4y ago
  No, they don't. At least nothing IDE specific. Most languages come with a way to configure dependencies and build configuration independently from IDEs. If your IDE is incapable of picking those up, your IDE is crap. If you want to keep your developers from having to muck about with IDE settings, put those settings into an independent repo. If your IDE is incapable of picking up configuration from a specific directory, again, your IDE is crap. Does your CI read IDE settings or language specific settings? If you're depending on IDE specific settings in your pipeline, your entire pipeline is brittle. So, no "sufficiently complex project" should need any IDE specific config in the project repo.
  - tekknik 4y ago
    Did you actually read the files? It’s launch configs and an eslint config. So you’re saying an IDE is crap if it can’t discover all of the commands of your project? Your saying it’s crap because in a split go and typescript codebase it’s supposed to know you want eslint triggered on JS code only during save? Using your logic, any IDE with a settings dialog is crap… See how ridiculous this sounds? It sounds more so like you hate VSCode
    - AnonymousPlanet 4y ago
      > Using your logic, any IDE with a settings dialog is crap… You are reading things into my comment that aren't there. Maybe you should reread it. Especially the part where I talk about the separation of project specific configs and general IDE configs. Or how your CI should be able to pick these things up. > It sounds more so like you hate VSCode What else are you seeing down there in the tea leaves? Did I say anything about VSCode?
      - tekknik 4y ago
        Perhaps you misread mine. What common structure exists to define what commands, sub commands, and tests exist in a project? If I were to write a CLI app, can any of the jetbrains or other IDEs automatically detect what the sub commands are within my CLI? What structure would it read this from? Golang certainly has no such file, so you’d have to read from the main package and understand every CLI framework out there to parse out the sub commands to build your launch configuration. Sounds real easy right? Now if we’re talking about nodejs, where the package.json can hold your run configurations within the script section, then ok. But we’re talking about golang.
Matthias247 4y ago
You can open the files in it and see what it does. It's absolutely nothing standard that you couldn't do without it. But having it committed will help others to use the same workflows more easily.
kitd 4y ago
It contains some useful debug launch configs that would take time to work out otherwise, and also some settings that appear to make the Node part and Go part work it bit more nicely together. I don't think there are any red flags there IMHO.
hogyncymraeg 4y ago
Nope. Just an old directory that made it in there at some point.

.vscode committed to a repository is a bit of a warning flag to me. It tells me this repo is doing some non-standard stuff that needs special IDE configuration to account for.

elashri 4y ago

or using codespaces for development

mcluck 4y ago

Or it just includes some conveniences. A lot of my projects include a .vscode folder so that anyone who uses VS Code can debug the application right away. If you want to use your own IDE or even just run everything from the terminal, it all still works.

skrtskrt 4y ago

Sufficiently complex projects are going to need some IDE config to get everything running and integrated with IDE tooling.

AnonymousPlanet 4y ago
No, they don't. At least nothing IDE specific. Most languages come with a way to configure dependencies and build configuration independently from IDEs. If your IDE is incapable of picking those up, your IDE is crap. If you want to keep your developers from having to muck about with IDE settings, put those settings into an independent repo. If your IDE is incapable of picking up configuration from a specific directory, again, your IDE is crap. Does your CI read IDE settings or language specific settings? If you're depending on IDE specific settings in your pipeline, your entire pipeline is brittle. So, no "sufficiently complex project" should need any IDE specific config in the project repo.
- tekknik 4y ago
  Did you actually read the files? It’s launch configs and an eslint config. So you’re saying an IDE is crap if it can’t discover all of the commands of your project? Your saying it’s crap because in a split go and typescript codebase it’s supposed to know you want eslint triggered on JS code only during save? Using your logic, any IDE with a settings dialog is crap… See how ridiculous this sounds? It sounds more so like you hate VSCode
  - AnonymousPlanet 4y ago
    > Using your logic, any IDE with a settings dialog is crap… You are reading things into my comment that aren't there. Maybe you should reread it. Especially the part where I talk about the separation of project specific configs and general IDE configs. Or how your CI should be able to pick these things up. > It sounds more so like you hate VSCode What else are you seeing down there in the tea leaves? Did I say anything about VSCode?
    - tekknik 4y ago
      Perhaps you misread mine. What common structure exists to define what commands, sub commands, and tests exist in a project? If I were to write a CLI app, can any of the jetbrains or other IDEs automatically detect what the sub commands are within my CLI? What structure would it read this from? Golang certainly has no such file, so you’d have to read from the main package and understand every CLI framework out there to parse out the sub commands to build your launch configuration. Sounds real easy right? Now if we’re talking about nodejs, where the package.json can hold your run configurations within the script section, then ok. But we’re talking about golang.

Matthias247 4y ago

You can open the files in it and see what it does. It's absolutely nothing standard that you couldn't do without it. But having it committed will help others to use the same workflows more easily.

kitd 4y ago

It contains some useful debug launch configs that would take time to work out otherwise, and also some settings that appear to make the Node part and Go part work it bit more nicely together. I don't think there are any red flags there IMHO.

hogyncymraeg 4y ago

Nope. Just an old directory that made it in there at some point.