Errors in IDE or Linter Autocompletion and Type Checking #645

Activity

1. github-actions

   added

   t-toolingIssues with this label are in the ownership of the tooling team.Issues with this label are in the ownership of the tooling team.

   on Nov 2, 2024
2. janbuchar commented on Nov 2, 2024

   

   janbuchar

   on Nov 2, 2024

   Collaborator

   More actions

   Hello and thank you for your interest in Crawlee! I'm afraid this issue is not exactly actionable in this state. Could you provide an example of such error and which IDE it appears in?
3. mgunawardhana commented on Nov 3, 2024

   

   mgunawardhana

   on Nov 3, 2024

   Last edited by mgunawardhana

   Author

   More actions

   # module_a.py
   from __future__ import annotations
   
   class ClassA:
       def method_a(self) -> ClassB:
           pass

   # module_b.py
   from __future__ import annotations
   from module_a import ClassA
   
   class ClassB:
       def method_b(self) -> ClassA:
           pass

   In this setup, if your IDE (say, VS Code or PyCharm) or linter does not fully support deferred annotations, it may not recognize ClassB in method_a or ClassA in method_b as valid references. This can lead to false positive warnings like "Cannot find reference" or missing autocomplete options when trying to use ClassB or ClassA.
4. janbuchar commented on Nov 4, 2024

   

   janbuchar

   on Nov 4, 2024

   Collaborator

   More actions

   In this setup, if your IDE (say, VS Code or PyCharm) or linter does not fully support deferred annotations, it may not recognize...

   But they both do support it, right? Deferred annotations are a part of the language, and have been so for a couple of years, so if a tool does not support them, that's an issue with the tool.

   Is there any non-hypotethical problem we could help with?

   👍React with 👍1Reacted by Vlada Dusek
5. apify

   locked and limited conversation to collaborators on Nov 11, 2024
6. B4nan

   converted this issue into a discussion #678 on Nov 11, 2024