Skip to content
This repository was archived by the owner on Apr 14, 2022. It is now read-only.
This repository was archived by the owner on Apr 14, 2022. It is now read-only.

Show warning for undeclared variables #242

Closed

Description

Also variables used before declaration

Activity

  1. MikhailArkhipov commented on Oct 15, 2018

    @MikhailArkhipov
    Author

    Adding sprint to we can start investigation since #19 needs this.

  2. jakebailey commented on Oct 16, 2018

    @jakebailey
    Member

    For the sake of writing it down, the plan is to add a new class to encapsulate "diagnostics" like undeclared variables, unknown imports, non-callables, etc, keep track of them in the analyzer, then later expose those with filtering, and past that, generate code actions from those diagnostics.

  3. jakebailey commented on Oct 17, 2018

    @jakebailey
    Member

    After going through everything, it turns out that PythonAnalyzer._diagnostics already basically encapsulates what we're looking for. There's already code in place for undeclared names and code for missing imports (with an associated message). It should just need some tweaking to better define when diagnostics are created and filtered.

  4. jakebailey commented on Oct 18, 2018

    @jakebailey
    Member

    image

  5. added a commit that references this issue on Oct 23, 2018
    48c406e
  6. added a commit that references this issue on Nov 1, 2019
    038e46a
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions