-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
Enhancement: naming-convention ignore imported types #6744
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
Comments
That's not strictly true - you can alias imported names: import { ajax as Ajax } from 'jquery'; Please also fill out the template. Entering n/a when you're requesting an enhancement makes it hard for us to understand things without asking more information Duplicate of #2106 |
That's not what I mean - I mean the ajax function needs me to pass an object to it: $.ajax({
type: 'GET',
url: '/something/something',
data: {
something: something
},
dataType: 'json',
success: function() {
// do something
}
}); and all of those property names ( But if I change them to match my naming rule the jQuery won't recognize what I sent it. |
Going back to my previous point... You included no code samples and described a different scenario. Again - this is why we have an issue template with required fields - so you can clearly describe the problem with clear examples to remove any misunderstanding and back-and-forth. Regardless, duplicate of #2244 |
Before You File a Proposal Please Confirm You Have Done The Following...
My proposal is suitable for this project
Link to the rule's documentation
https://typescript-eslint.io/rules/naming-convention/
Description
I have no control over the naming conventions of imported types, so the naming-convention rule that I set up for my code is throwing errors everywhere I interact with imported code that needs me to pass it an object e.g. the jQuery
ajax
function.Fail
Pass
Additional Info
No response
The text was updated successfully, but these errors were encountered: