Skip to content

chore(agglayer): address review nits from #2955#2957

Merged
mmagician merged 3 commits into
nextfrom
mmagician-claude/agglayer-port-comment-fixups
May 21, 2026
Merged

chore(agglayer): address review nits from #2955#2957
mmagician merged 3 commits into
nextfrom
mmagician-claude/agglayer-port-comment-fixups

Conversation

@mmagician
Copy link
Copy Markdown
Collaborator

@mmagician mmagician commented May 20, 2026

Summary

Follow-up to #2955

Commit 1 — docs(agglayer): drop port-narrative phrases from faucet docstrings

Addresses:

Commit 2 — test(agglayer): always construct deterministic destination account

Addresses:

The conditional matches!(data_source, ClaimDataSource::L1ToMiden | ClaimDataSource::L2ToMiden) was removed. Also, flattened Option<Account> to Account, and re-indented the if let Some(...) consume block to match the pattern in the file's other tests.

🤖 Generated with Claude Code

claude added 2 commits May 20, 2026 09:21
The "conversion metadata lives on the bridge" clause was useful for the
PR #2771 / #2955 port narrative but is not load-bearing for readers of
the merged code. Trim it from the AggLayerFaucet docstring in lib.rs and
the inline comment in faucet.rs.
The conditional matches! arm in test_bridge_in_claim_to_p2id enumerates
both ClaimDataSource variants (L1ToMiden | L2ToMiden) — the only two —
so the branch is always taken and the Option<Account> wrapping forces a
needless if let Some(...) around the post-mint consume+assert block.

Construct destination_account unconditionally and flatten the consume
block to match the pattern used by the other bridge_in tests.
@mmagician mmagician added the no changelog This PR does not require an entry in the `CHANGELOG.md` file label May 20, 2026
@mmagician mmagician marked this pull request as ready for review May 20, 2026 09:50
@mmagician mmagician added agglayer PRs or issues related to AggLayer bridging integration pr-from-maintainers PRs that come from internal contributors or integration partners. They should be given priority labels May 20, 2026
Copy link
Copy Markdown

@flamiinngo flamiinngo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The docstring cleanup is the right call implementation docs shouldn't carry PR-narrative context that becomes misleading once merged. The test simplification in bridge_in.rs is correct; the matches! guard was redundant since L1ToMiden and L2ToMiden are the only two ClaimDataSource variants, so the check always evaluated to true.
Flattening to an unconditional construction makes the intent clearer.

Copy link
Copy Markdown
Contributor

@partylikeits1983 partylikeits1983 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for opening a PR to clean this up

@mmagician mmagician added this pull request to the merge queue May 21, 2026
Merged via the queue into next with commit 8660a8e May 21, 2026
20 checks passed
@mmagician mmagician deleted the mmagician-claude/agglayer-port-comment-fixups branch May 21, 2026 11:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

agglayer PRs or issues related to AggLayer bridging integration no changelog This PR does not require an entry in the `CHANGELOG.md` file pr-from-maintainers PRs that come from internal contributors or integration partners. They should be given priority

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants