Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VSCode Extension doesn't use extension settings #674

Open
rfuzzo opened this issue Sep 13, 2024 · 2 comments
Open

VSCode Extension doesn't use extension settings #674

rfuzzo opened this issue Sep 13, 2024 · 2 comments

Comments

@rfuzzo
Copy link

rfuzzo commented Sep 13, 2024

Hej,

it seems the VSCode extension does not use the extension formatter settings at all.

  • I checked compact entries, but nothing is formatted
  • in the workspace, all toml files display "this document has been excluded"
  • adding a .taplo.toml with includes does nothing

Is there anything I am missing?

@redeboer
Copy link
Contributor

redeboer commented Oct 4, 2024

The VS Code extension should recognize .taplo.toml (we use it in all our repositories), but you have to reload the window (restart) if you modify any of the settings there.

The VS Code extension does not respect all the latest configuration options though, because it is outdated. See #624 (comment).

@morphatic
Copy link

Here's what worked for me to get the VS Code extension to recognize my custom rules:

  1. Put a file called .taplo.toml in the root of your project with the configuration settings
  2. Close VSCode and re-open it

Here are things that did NOT work. I tried saving and restarting VSCode after each one:

  • Naming the config file taplo.toml
  • Putting the following settings in either my User settings.json or .vscode/settings.json
{
    // ... other VSCode settings ...
    "evenBetterToml.rules": [
        {
            "path": "rust-toolchain.toml",
            "rules": {
                "schema": {
                    "enabled": false
                }
            }
        }
    ]
}

Note, I was trying to resolve the same issue as described here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants