Mikhail Golubev 4aff3ed154 PY-83039 Don't trigger PyLiteralTypeCompletionContributor in cases like x = y.foo<caret> ...

It should be activated only for the simplest cases when the caret is either
inside an immediate string literal or its prefix is an unqualified reference
expression. It makes little sense trying to detect if something like
the literal string `"y.foobar"` is a possible value for `x`.

It's a relatively heavy completion contributor. It starts evaluating the type of
`x` flow-sensitively, analyzing all preceding function calls to take into
account `NoReturn`. It affects common workflows like typing out
`df = pd.` to create a new Pandas dataframe.


(cherry picked from commit f17fe2ce86ee100a3480a574c7f57a1bd67ec2d8)

IJ-CR-172165

GitOrigin-RevId: 4434488b1d2dae3ab7efd72e775b0c730268e51c

2025-08-18 11:48:31 +00:00

..

gen/com/jetbrains/python/psi/types

…

resources

PY-82168: Implement inspection and quick fixes for dataframe and series in the conditions

2025-08-08 19:31:55 +00:00

src/com/jetbrains/python

PY-83039 Don't trigger PyLiteralTypeCompletionContributor in cases like x = y.foo<caret>

2025-08-18 11:48:31 +00:00

BUILD.bazel

[PY-82607] introduce a caching for all computations in PyTypingTypeProvider

2025-08-03 21:40:01 +00:00

intellij.python.psi.impl.iml

[PY-82607] introduce a caching for all computations in PyTypingTypeProvider

2025-08-03 21:40:01 +00:00