Figure out recursive querying #2

New issue

Open

opened 2026-05-08 03:16:46 +00:00 by gotmax23 · 1 comment

gotmax23 commented

2026-05-08 03:16:46 +00:00

Owner

# TODO(!!!): Figure out how to handle recursive querying (e.g., bar -> foo -> some-orphaned-package),
# specifically how to represent that in the outputs (JSON data and text
# reports) or whether that's something we want to implement here to begin with.

``` # TODO(!!!): Figure out how to handle recursive querying (e.g., bar -> foo -> some-orphaned-package), # specifically how to represent that in the outputs (JSON data and text # reports) or whether that's something we want to implement here to begin with. ```

gotmax23 referenced this issue

2026-05-08 15:53:04 +00:00

Write script to compare the list of affected packages found by v2 vs. v1 #12

gotmax23 commented

2026-06-12 05:57:37 +00:00

Author

Owner

Before I overengineer recursive querying¹, I'd like to figure out report generation and formatting based on a single level of dependency resolution (#3 and #4).

Recursive querying isn't horribly complicated. The main question/problem is how to incorporate more than one level of an orphaned package's reverse dependency tree into the text and JSON reports in a logical way (which I don't necessarily think v1 necessarily succeeded in doing). ↩︎

Before I overengineer recursive querying[^1], I'd like to figure out report generation and formatting based on a single level of dependency resolution (#3 and #4). [^1]: Recursive querying isn't horribly complicated. The main question/problem is how to incorporate more than one level of an orphaned package's reverse dependency tree into the text and JSON reports in a logical way (which I don't necessarily think v1 necessarily succeeded in doing).

gotmax23 added the

Priority

Medium

label

2026-06-29 19:17:45 +00:00