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
Hello! Many thanks to your effort on trying to make django-stubs compatible with Pylance.
I tried this package and the intelliSense for Foreignkey works nicely. However, the other fields such as DecimalField, PositiveSmallIntegerField, etc. are still interferred to Any when being called.
I've added django-autotyping to INSTALLED_APPS, and run the command generate_stubs. The stubs for my models are generated under the folder typings. I then add typings to Pylance's settings python.analysis.stubPath.
Is there anything I missed? Thank you.
The text was updated successfully, but these errors were encountered:
Hello, thanks for the feedback. I'm planning on fixing the issue you are describing directly in the stubs. I have a pending PR for this: typeddjango/django-stubs#1900.
Unfortunately, it requires non trivial changes in the mypy plugin, and I would also like to use a better solution (something as described in microsoft/pyright#6914), but would require mypy to support python/mypy#3737.
Hello! Many thanks to your effort on trying to make django-stubs compatible with Pylance.
I tried this package and the intelliSense for Foreignkey works nicely. However, the other fields such as DecimalField, PositiveSmallIntegerField, etc. are still interferred to Any when being called.
I've added django-autotyping to INSTALLED_APPS, and run the command generate_stubs. The stubs for my models are generated under the folder typings. I then add typings to Pylance's settings python.analysis.stubPath.
Is there anything I missed? Thank you.
The text was updated successfully, but these errors were encountered: