Skip to content

no-async-in-computed-properties fails on objects containing async functions #725

Closed
@cjpearson

Description

@cjpearson

This can be seen on the demo page for the rule here. Adding the following computed property causes an ESLint error.

test () {
  return {
    callback: async (e) => e
  }
}

What did you expect to happen?
No error since computing the result of the computed property is not asynchronous.

What actually happened?
There is an error on the property.

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions