Skip to content

Why is ErrorKind::details not formatted? #1992

@katrinafyi

Description

@katrinafyi

The indentation is way too much in some places and it doesn't get picked up by cargo fmt or detected by the formatting check. Removing the clippy annotation doesn't seem to change the behaviour.

pub fn details(&self) -> Option<String> {
match self {
ErrorKind::NetworkRequest(e) => {
// Get detailed, actionable error analysis
Some(utils::reqwest::analyze_error_chain(e))
}
ErrorKind::RejectedStatusCode(status) => Some(

Other functions in the same file get formatted as you'd expect.

I know that macros can interfere with rustfmt, but it doesn't look like this code is within any macros.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    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