Manage extension settings

My Prettier extension is reformatting files with tabs but this project uses two spaces. Change the extension settings for this workspace to set tabWidth to 2 and useTabs false, and make sure the formatter runs on save. Confirm by saving the README.md and showing the indentation uses two spaces.

Before I change workspace settings for the formatter, identify any conflicting settings sources: workspace settings.json, .editorconfig, project-level Prettier config file, and repository CI formatting checks. Surface the single setting that will win and flag anything that would still force tabs. Provide me the exact settings snippet to paste into the workspace settings.json to enforce two spaces reliably.

I set tabWidth to 2 in the workspace settings but files still format with tabs when I save. I suspect an .editorconfig or a project-level prettier config overrides it. Which files should I inspect in order, what exact lines in each indicate tabs will win, and the minimal edits to make workspace settings authoritative without breaking the shared repo rules?

Across several repos I spend time toggling extension settings so local editor behavior matches each project. This costs minutes per setup and causes commit noise. Recommend a pattern to reduce friction: which settings to centralize, when to prefer project config files, a team convention to avoid local overrides, and a short checklist to onboard new members so they don’t flip settings repeatedly.