-
-
Notifications
You must be signed in to change notification settings - Fork 18.2k
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
STYLE: Resolved Inconsistent namespace #40286
Conversation
deepang17
commented
Mar 7, 2021
•
edited
Loading
edited
- closes STYLE Increase coverage of inconsistent-namespace-usage #39992
- tests added / passed
- Ensure all linting tests pass, see here for how to run them
- whatsnew entry
Hi @deepang17 - instead of excluding a file, can we change |
Sure, will do that. |
Thanks @deepang17 , I'll just mark this as draft pending on #39992 (comment) , will then reopen (depending on what we hear back, you may need to rebase / fix conflicts) |
Hi @deepang17 - #40310 is in, do you want to rebase and fix up any remaining errors so we can get this in? |
Hello, @MarcoGorelli I have completed work from my side. If you think that changing from |
You'll also need to change it to
It's just a variable in a test, so it's not a breaking change If you could fetch and merge upstream/master and fixup "unique" in |
Ok, will do that. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for updating - there's still some files to be fixed up though, which are failing the pre-commit check
@MarcoGorelli these new files are producing the error. |
Shall I convert them to arrays? |
I'd suggest renaming to |
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've made some suggestions for some files, for the others I think arr
might work (if not, please let me know for which ones it doesn't)
@MarcoGorelli it's ready to be merged. Thank you for your guidance. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @deepang17
it's ready to be merged
I admire your confidence :) Still have some comments though, I think some of these names are unclear and that arr
should work in those files
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me pending green, cc @jbrockmendel / @jorisvandenbossche for any further comments
Hi @deepang17 - can you fetch and merge upstream/master please? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I went ahead and renamed the rest of these *_array
to arr
and they seem to be fine, not sure why you said there'd be conflicts - perhaps it was just the fixture?
Great, at that time some other variables were also used with the name |
Thanks @deepang17 ! |