Skip to content

fix: resolve roxygen2 warnings#2692

Merged
schochastics merged 2 commits into
mainfrom
fix-roxygen-warnings-2679-followup
Jun 5, 2026
Merged

fix: resolve roxygen2 warnings#2692
schochastics merged 2 commits into
mainfrom
fix-roxygen-warnings-2679-followup

Conversation

@schochastics

@schochastics schochastics commented Jun 5, 2026

Copy link
Copy Markdown
Contributor

fix #2641

Summary

Follow-up to #2690 / #2679. Now that roxygenize() no longer swallows errors and the docs are actually regenerated in CI, roxygen2 surfaces several real issues that were previously hidden. This fixes them at the source (roxygen comments only — Rd/NAMESPACE are regenerated in CI).

Fixes

  • @aliases must be a single line (roxygen2 8.x): collapse the wrapped tags in cohesive.blocks.R and layout.R.
  • Unregistered S3 methods: several methods carried only a @method tag and were never registered in NAMESPACE (roxygen never ran successfully before). Added @export so they are registered via S3method():
    • as.data.frame.igraphSDF, [.igraphSDF, [<-.igraphSDF
    • as.dendrogram.igraphHRG (mirrors the already-exported as.dendrogram.communities)

Not changed

The @details refers to un-installed package ape message is a local-only artifact — ape is a Suggests and is installed in CI (deps::. pulls the root package's soft deps), where [ape::as.phylo()] resolves. Rewriting the valid cross-reference would be wrong.

schochastics and others added 2 commits June 5, 2026 08:08
With roxygenize() no longer swallowing errors, roxygen2 now reports
several real issues:

- @Aliases tags must be a single line (cohesive.blocks.R, layout.R);
  collapse the wrapped tags.
- Several S3 methods had only a @method tag and were never registered
  in NAMESPACE because roxygen never ran successfully. Add @export so
  they are registered: as.data.frame/[/[<-.igraphSDF and
  as.dendrogram.igraphHRG (matching as.dendrogram.communities).
@github-actions

github-actions Bot commented Jun 5, 2026

Copy link
Copy Markdown
Contributor

This is how benchmark results would change (along with a 95% confidence interval in relative change) if f638852 is merged into main:

  • ✔️as_adjacency_matrix: 669ms -> 667ms [-1.9%, +1.29%]
  • ✔️as_biadjacency_matrix: 665ms -> 668ms [-0.49%, +1.13%]
  • ✔️as_data_frame_both: 1.59ms -> 1.55ms [-7.5%, +2.33%]
  • ✔️as_long_data_frame: 4ms -> 4.03ms [-1.12%, +2.44%]
  • ✔️es_attr_filter: 2.97ms -> 2.93ms [-3.95%, +1.32%]
  • ✔️graph_from_adjacency_matrix: 108ms -> 108ms [-1.3%, +2.07%]
  • ✔️graph_from_data_frame: 3.41ms -> 3.43ms [-0.99%, +1.75%]
  • ✔️vs_attr_filter: 1.63ms -> 1.63ms [-2.11%, +2.39%]
  • ✔️vs_by_name: 1.05ms -> 1.06ms [-1.34%, +3.54%]
    Further explanation regarding interpretation and methodology can be found in the documentation.

@schochastics schochastics changed the title fix: resolve roxygen2 warnings surfaced after #2679 fix: resolve roxygen2 warnings Jun 5, 2026
@schochastics schochastics merged commit 8764dfa into main Jun 5, 2026
1 check passed
@schochastics schochastics deleted the fix-roxygen-warnings-2679-followup branch June 5, 2026 06:36
@maelle

maelle commented Jun 5, 2026

Copy link
Copy Markdown
Contributor

Danke!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

roxygen2 warnings

2 participants