Bug: The `Reflect.getOwnPropertyNames` still doesn't exist

Environment

Node version: v16.17.0 npm version: v8.18.0 Local ESLint version: v8.23.0 (Currently used) Global ESLint version: v8.23.0 Operating System: linux 5.4.0-1089-azure

What parser are you using?

Default (Espree)

What did you do?

Configuration

{
    "env": {
        "browser": true,
        "jquery": true,
        "es6": true,
        "es2020": true,
        "es2021": true
    },
    "parserOptions": {
        "ecmaVersion": "latest"
    },
    "extends": "eslint:recommended",
    "rules": {
        "prefer-reflect": "error"
    }
}

Code:

        function getOwnPropertyNamesLength(obj) {
            return Object.getOwnPropertyNames(obj).length;
        }

What did you expect to happen?

Due to the function Reflect.getOwnPropertyNames still doesn’t exist (I can’t even find it in caniuse.com), the rule prefer-reflect should not consider about it, so does the document.

What actually happened?

The rule complain that “Avoid using Object.getOwnPropertyNames, instead use Reflect.getOwnPropertyNames.”

Participation

• I am willing to submit a pull request for this issue.

Additional comments

I knew that #7075 is about it and closed, but I met the problem again, that’s why I submit this issue.

[mdjermanovic]

that’s a fair point, but it’s just Reflect.ownKeys(x).filter(x => typeof x === 'string') ¯_(ツ)_/¯

That would work, but this rule wasn’t intended to suggest replacements of such complexity, so I think it’s fine to add a note in the docs that Object.getOwnPropertyNames was added by mistake.

[AnnAngela]

@mdjermanovic OK, I will make a PR to change the documents only.