Skip to content

cargo sort sets expectations beyond sorting #182

@sandersaares

Description

@sandersaares

We use the cargo sort utility to maintain order in our Cargo.toml files. However, this utility also appears to set expectations that go beyond just sorting - it also sets expectations on formatting!

These expectations are rather intrusive, e.g expecting specific newlines here or there, whereas VS Code plugins like "Even Better TOML" will format TOML files differently.

We need to resolve this conflict - cargo sort should stick to ordering and not try have a say about formatting.

Even Better TOML

[package.metadata.cargo_check_external_types]
allowed_external_types = [
    "bytesbuf::*",
    "ohno::*",
    "futures_core::stream::Stream",
]

cargo-sort

[package.metadata.cargo_check_external_types]
allowed_external_types = ["bytesbuf::*", "ohno::*", "futures_core::stream::Stream"]

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions