Resolve Pylance/Pylint overlap (optionally?)

[ewerybody]

I see Pylance and Pylint have different uses and I truly love them both but there IS some overlap, right?
To mitigate having double the amount of problems listed I already gathered a list of disable flags for Pylint for things that are already handled by Pylance sufficiently (this is probably incomplete!)

import-error,no-member,no-name-in-module,unused-variable,unused-argument,attribute-defined-outside-init,unused-import,
undefined-loop-variable,access-member-before-definition,undefined-variable,pointless-statement,no-value-for-parameter

But these are now both MS projects! Wouldn't it be rather trivial to find that Pylance is also used to disable these things automatically or at least optionally? :)
Thank you
ëRiC

[karthiknadig]

Thanks for the feature request! We are going to give the community 60 days from when this issue was created to provide 7 👍 upvotes on the opening comment to gauge general interest in this idea. If there's enough upvotes then we will consider this feature request in our future planning. If there's unfortunately not enough upvotes then we will close this issue.