Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

allow publishing a more detailed graph #15195

Open
purajit opened this issue Dec 30, 2024 · 0 comments
Open

allow publishing a more detailed graph #15195

purajit opened this issue Dec 30, 2024 · 0 comments
Labels
analyze Related to Ruff analyze functionality needs-decision Awaiting a decision from a maintainer

Comments

@purajit
Copy link
Contributor

purajit commented Dec 30, 2024

In addition to the options to publish the graph based on module paths and including third-party deps
mentioned in #13431, publishing a --detailed graph would be great! It would allow people to build or
conceive of several other tools on top of ruff, and also allow ruff to swallow them up.

This could include information like:

  • whether this is from a string or not
    • if it could go so deep as to being able to detect whether it's being mocked, dynamically imported,
      opened as a pkg resource, etc, that would be absolutely nuts
  • whether this is a top-level import or not
  • whether private members are imported (I guess this starts pushing the graph towards being not
    just for modules but for module members)
  • whether it's a relative import
  • any attached annotations (particularly pylint, also semgrep)

I understand there would be some non-trivial restructure or reconsideration, since there could be multiple
dependencies on the same module with differing characteristics

@MichaReiser MichaReiser added needs-decision Awaiting a decision from a maintainer analyze Related to Ruff analyze functionality labels Dec 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
analyze Related to Ruff analyze functionality needs-decision Awaiting a decision from a maintainer
Projects
None yet
Development

No branches or pull requests

2 participants