• 1 Post
  • 30 Comments
Joined 2 years ago
cake
Cake day: July 7th, 2023

help-circle


  • Eager Eagle@lemmy.worldtoProgrammer Humor@programming.dev.DS_Store
    link
    fedilink
    English
    arrow-up
    3
    arrow-down
    1
    ·
    2 days ago

    Absolutely nothing wrong. Their whole argument is that it delivers no guarantees about the things set in these files, but setting these presets is more about convenience than enforcing an equal development environment.

    Whoever needs to enforce things like formatting and linting at the project level should be using a CI step.


  • Eager Eagle@lemmy.worldtoProgrammer Humor@programming.dev.DS_Store
    link
    fedilink
    English
    arrow-up
    3
    arrow-down
    1
    ·
    2 days ago

    Can we stop with the absolutes?

    It’s okay to commit IDE config if your team uses mostly one editor.

    It’s also okay to include extension recommendations. While extensions may not be needed to run the code, depending on the editor and language they’re highly desirable. It’s that kind of extension that should be recommended. I’m sure there’s a setting to disable them if, for some reason, the editor keeps asking you.






  • Eager Eagle@lemmy.worldtoProgrammer Humor@programming.dev.DS_Store
    link
    fedilink
    English
    arrow-up
    3
    arrow-down
    1
    ·
    edit-2
    2 days ago

    .vscode doesn’t store cache or any trash like that, so if you’re including all settings, tasks, etc, you can probably just include everything.

    The only thing to keep in mind is to only add settings, extension recommendations, etc that apply to all your collaborators and aren’t just personal preferences. A few good examples are formatting rules, task definitions to run the project, and linting rules that can’t be defined somewhere else.