Tatsh / instagram-archiver / 25616499533

100%

push

github

project: archive child (reply) comments

Add a `--include-child-comments`/`-R` flag that, after the existing
top-level comment fetch, recursively walks each parent comment with
`child_comment_count > 0` and embeds the full reply set under the
parent's `child_comments` key in the saved per-post
`<id>-comments.json`. Closes the first checkbox of issue #3 (the
second was closed by the previous reels image commit).

CLI:

- New `-R`/`--include-child-comments` flag on `instagram-archiver`,
  applicable to both profile and `--saved` modes. Help text notes
  that it implies `--include-comments`.
- `_async_profile_main` and `_async_saved_main` gain
  `include_child_comments` keyword.

Scrapers:

- `ProfileScraper.__init__` and `SavedScraper.__init__` gain a
  `child_comments` keyword. `should_save_comments` is now
  `comments or child_comments` so `-R` automatically activates the
  comments worker; `should_save_child_comments` is set
  independently. This avoids a confusing footgun where asking for
  replies but no parents would fetch nothing.

Client:

- New `should_save_child_comments` attribute on `InstagramClient`,
  defaulted to `False`.
- New private `_fetch_child_comments(media_id, comment_pk)` paginates
  the `comments/{comment_pk}/child_comments/` endpoint with
  `min_id`/`is_chronological=true`/`paging_direction=view_more`. On
  HTTPError it returns whatever pages were already collected
  (only fully `None` when the first request fails), so a transient
  failure mid-pagination still preserves what we have.
- New private `_embed_child_comments(media_id, comments)` walks the
  combined top-level comment list and enriches each parent in place.
  Comments without a `pk` (or `id` fallback) are skipped with a
  debug log instead of a crash.
- `save_comments` calls the embed step after the existing pagination
  loop when `should_save_child_comments` is `True`.

Typing:

- New `ChildCommentsPage` TypedDict in `instagram_archiver.typing`
  with `child_commen... (continued)

137 of 137 branches covered (100.0%)

Branch coverage included in aggregate %.

49 of 49 new or added lines in 5 files covered. (100.0%)

1070 of 1070 relevant lines covered (100.0%)

5.0 hits per line