Skip to content

Bug: @typescript-eslint/require-await should not be recommended #11731

@runspired

Description

@runspired

Recommended rules should represent best practices. At a minimum, using async without await is not a bad practice, and in most usages it represents a best practice helping to safeguard the invocation and API surface. The alternative is both more brittle and more verbose, prone to accidentally leaking synchronously thrown errors.

What's more, linting against using recommended language features - especially in a way that changes behavior - is just odd.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingpackage: eslint-pluginIssues related to @typescript-eslint/eslint-plugintriageWaiting for team members to take a look

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions