Skip to content

Format on save -feature is too aggressive #138

Description

@Tuupertunut

The editor.formatOnSave feature for VS Code is causing problems for me when saving files. If I don't yet have Biome installed, it will forcefully format my code with Prettier every time I try to save. The same happens if there is a problem in the biome.json config, it will forcefully format my code with the wrong config. These issues are preventing me from saving files, because the files get mangled into the wrong format every time I try.

I think formatting is something that a developer should do before saving (Ctrl+Shift+I in VS Code), but it should not prevent one from saving a file in the wrong format if necessary.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions