Rule Change: no-obj-calls should support Intl?

[sosukesuzuki]

What rule do you want to change?

no-obj-calls

What change to do you want to make?

Generate more warnings

How do you think the change should be implemented?

A new default behavior

Example code

Intl();
new Intl();

What does the rule currently do for this code?

No errors.

What will the rule do after it's changed?

Error: 'Intl' is not a function

Participation

• I am willing to submit a pull request to implement this change.

Additional comments

I know Intl isn't defined in ECMA-202. But it is is defined in ECMA-402 that is internationalization API for ECMA-202.
Also it is implemented in both browsers and Node.js, so I think it make sense that no-obj-calls support Intl.

[nzakas]

I think this makes sense. Would like some feedback from the rest of the team.

[mdjermanovic]

The Internationalization API is optional, so a global Intl could be something else. Though, that's unlikely. I don't have a strong opinion. If others think that core rules should treat Intl as a known built-in global, I'll agree.

[snitin315]

This makes sense to me 👍🏻, I suppose rules treat Intl as global when the environment is the browser

[snitin315]

We have 3 👍🏻, marking it as accepted. @sosukesuzuki feel free to send a PR if you are interested.