Thanks again @caleb531, someone will take a look as soon as they can ✌️

Failure looks unrelated, we restarted it but same error.

👋 Hi @caleb531: Thanks for this! 🙇 I tested this out locally, and I do see that this pull request causes the arrow function parameters to have a new scope, but I don't see any change to the syntax highlighting. It's possible that I'm doing something wrong, so I'll show you what I'm seeing, and you can let me know if I'm missing something. 😅

Note: All of the examples below are using Atom 1.42.0-nightly1 and the monokai syntax theme.

With Tree-Sitter parsers disabled

With Tree-Sitter parsers enabled

With Tree-Sitter parsers enabled using the changes from this pull request

I see that the formal-parameter scope gets applied, but I'm not sure if syntax themes are using that scope or not. Instead of applying the formal-parameter scope, should we instead apply the same scopes used in the TextMate grammar (i.e., meta-method-call meta.arguments meta.function.arrow meta.parameters variable.parameter.function)?

@jasonrudolph Ha, that's because it turns out I have the following styles in my styles.less:

atom-text-editor:not([mini]) .syntax--source.syntax--js .syntax--formal-parameter.syntax--identifier {
   color: @orange;
}

My apologies about that. But I agree, variable.parameter.function would be the way to go (as this scope is already used in the Python tree-sitter grammar, and the color of those parameters is already orange for monokai, as it should be)

But I agree, variable.parameter.function would be the way to go...

@caleb531: Cool. Wanna make that change?

@jasonrudolph Just pushed the rebased changes! The scope is now variable.parameter.function.

Just pushed the rebased changes!

Thanks, @caleb531! 🚀