Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NoReservedKeywordParameterNames: more specific error indicator #107

Merged

Conversation

jrfnl
Copy link
Member

@jrfnl jrfnl commented Mar 19, 2022

The warning for reserved keywords used in parameter names would previously be thrown on the line (+ column) where the function keyword for the function declaration was found.

This commit changes that to pinpoint the exact location of the reserved keyword used as a parameter name.

Includes adjusting one existing test to safeguard this (and safeguard handling with references and type declarations).

The warning for reserved keywords used in parameter names would previously be thrown on the line (+ column) where the `function` keyword for the function declaration was found.

This commit changes that to pinpoint the exact location of the reserved keyword used as a parameter name.

Includes adjusting one existing test to safeguard this (and safeguard handling with references and type declarations).
@jrfnl jrfnl added this to the 1.0.0-alpha4 milestone Mar 19, 2022
@jrfnl jrfnl enabled auto-merge March 19, 2022 18:16
@jrfnl jrfnl merged commit dbbcabc into develop Mar 19, 2022
@jrfnl jrfnl deleted the universal/noreservedkeywordparams-more-specific-warning-ptr branch March 19, 2022 18:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant