catch should not be a keyword when used in a Promise chain

[phortuin]

Currently, when parsing javascript, catch will be rendered as a keyword. Since ES6, catch is also a method on the Promise prototype, which is probably best rendered as a function in Prism:

fetch('some-resource.json')
    .then(response => response.json())
    .catch(console.error)

Hopefully, there is an easy way to test for this. Thanks!

[mAAdhaTTah]

I think if we highlight catch as a keyword only if it's not preceded by a dot, that would work?

[RunDevelopment]

In JS, catch is only used in try...catch blocks so we could say, that it will only a keyword if it's preceded by /}\s*/. (Same for finally.)
Like this, we should also be able to eliminate most false positives from identifiers and functions.

Or am I forgetting something?