Skip to content

Harper should attempt to detect mixing up "exacerbated" and "exasperated". #3886

Description

@hippietrail

I was just reading the comments after watching a YouTube video and one was about the presenter mixing up "flouting" and "flaunting" - which we already have an issue about if not a linter yet - but also about mixing up "exacerbated" and "exasperated" - which I don't believe has come up here before.

It is covered in online discussions though.

Examples from GitHub and Stack Overflow:

  • This problem is further exasperated if similar objects don't have an instance of a key or contain only one
  • The problem is further exasperated by the lack of documentation from AWS about the limits on this particular endpoint
  • I imagine a basic question that is exacerbating me.
  • The child window within the menu seems to be the exasperating factor here.
  • A few historic office buildings on key Chestnut blocks caught fire and were left in a state of disrepair for many years further exasperating the 'empty' feeling

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestharper-coreRelated to the core grammar checking enginelintingRelated to lint rules and linter execution

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions