Completions don't work for test parameters #4388
Replies: 10 comments 4 replies
-
I think this is worth considering. Instead of |
Beta Was this translation helpful? Give feedback.
-
With the recent VSCode IntelliSense improvements for pytest, I've started searching if it's a bug (at least it looks like a bug for someone from the outside). |
Beta Was this translation helpful? Give feedback.
-
@ciszko, please file a new issue on this and include some sample code to demonstrate the behavior that you want. |
Beta Was this translation helpful? Give feedback.
-
Do I need to create another issue if this one already exists? It's exactly what @rchiodo wrote. |
Beta Was this translation helpful? Give feedback.
-
Any progress regarding this issue ? It would be really helpful. |
Beta Was this translation helpful? Give feedback.
-
@night-as this is waiting for more people to up vote it, so no it's not on our backlog yet. |
Beta Was this translation helpful? Give feedback.
-
Moving to discussions to hopefully get more visibility. |
Beta Was this translation helpful? Give feedback.
-
Any update on this issue? |
Beta Was this translation helpful? Give feedback.
-
Not just completions, but I think it makes sense to have type checking as well, not sure it that all comes along together within pyright or not |
Beta Was this translation helpful? Give feedback.
-
What are the workarounds you guys currently use for this? I have to admit, it's quite annoying. It's also useful to check the discussion on the Pytest end (I tend to believe it's more of their issue than that of Pylance). I've found a fragile workaround:
The problem about it is casting the |
Beta Was this translation helpful? Give feedback.
-
Example code:
We could probably implement first level completions? If the type is any and its declaration is a parameter, get the type from the extensions?
Beta Was this translation helpful? Give feedback.
All reactions