sogerc1

Additional info: even though I have those two options cache files still appear in the DefinitionCache/Serializer directory if I give write permission in my development virtual machine.

I didn't open another issue, because I think mine is the same issue. This year intelephense started giving me error for this: `$val = pg_escape_literal(json_encode($val));` saying: Expected type 'PgSql\Connection' found...

There are more issues with type detection. See this example:  The error says expected array, found string. Interestingly if I remove the type hints from the comment in front...

Is there a way to temporarily disable the 1006 errors until this bug is fixed? Because right now the error reporting is completely useless, almost all opened files are shown...

Found it: `"intelephense.diagnostics.typeErrors": false` Disables quite a lot of error checks so be careful.

Issue still present in v1.12.1 I still have to keep "intelephense.diagnostics.typeErrors" on false which is not ideal.