Bug: [member-ordering] Not Detecting Order For Read-Only Fields Correctly about typescript-eslint

[bradzacher]

This may be a little counter-intuitive but it is working as intended.

The rule looks for "selectors" in a pre-defined order and it uses the specificity of the selector to determine what matches first.

For a public readonly field that is not static, the most specific selector for it is public-instance-readonly-field and the least specific is readonly-field.

In your example you have the least specific selector readonly-field and a more specific selector public-instance-field. So the member matches the latter selector before it matches the former. Meaning that both members match the same selector. Meaning the rule then uses your order config (alphabetical).

Given that you have granularly defined very specific selectors of *-instance-field et al - you also need to granularly define selectors for *-readonly-field so that the rule correctly matches. For example if you define public-instance-readonly-field instead of readonly-field then the rule works as intended playground