Rule proposal: Prefer readonly member variables instead of getters that return literal values, or vice versa

[c32hedge]

I'm finding a common pattern in our code:

  export class PageObject {
    get saveButton() {
      return '[data-testid="saveButton"]';
    }
  }

I would like to enforce using simple readonly members instead of getter functions:

  export class PageObject {
    readonly saveButton = '[data-testid="saveButton"]';
  }

This could also be applied to getter functions that return other literals, such as integers.

Some people prefer the reverse, so the rule should be bidirectional.

[sindresorhus]

I would prefer the inverse, as I make reusable packages that will be consumed by JS users too, and I want to ensure it can only be read from, not assigned.