You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey, it's pretty common for 3p code out of PIP to have incomplete or incorrect typing information.
Instead of having our local developers disable type-checking in order to get things working, I think it would be helpful to allow us to merge a local type stub (or an inline declaration of typing information near to the local usage) with the one coming from the imported module.
In this way, local developers can make progress if the upstream module is incorrect. My team, for instance, is stuck on old versions of modules for compatibility reasons and can't pick up the up-to-date correct typing information.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hey, it's pretty common for 3p code out of PIP to have incomplete or incorrect typing information.
Instead of having our local developers disable type-checking in order to get things working, I think it would be helpful to allow us to merge a local type stub (or an inline declaration of typing information near to the local usage) with the one coming from the imported module.
In this way, local developers can make progress if the upstream module is incorrect. My team, for instance, is stuck on old versions of modules for compatibility reasons and can't pick up the up-to-date correct typing information.
Beta Was this translation helpful? Give feedback.
All reactions