8000 feat: refactor settlement logic and use strong types for agglayer-types by Ekleog-Polygon · Pull Request #835 · agglayer/agglayer · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

feat: refactor settlement logic and use strong types for agglayer-types #835

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

Merged
merged 47 commits into from
Jun 30, 2025

Conversation

Ekleog-Polygon
Copy link
Contributor
@Ekleog-Polygon Ekleog-Polygon commented Jun 4, 2025

Fixes https://github.com/agglayer/protocol-research/issues/148
Fixes #661

Builds on top of #819

PR Checklist:

  • I have performed a self-review of my code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have added or updated tests that comprehensively prove my change is effective or that my feature works

@Ekleog-Polygon Ekleog-Polygon self-assigned this Jun 4, 2025
Copy link
Contributor
@iljakuklic iljakuklic left a comment

Choose a reason for hiding this comment

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

Just first pass over some of the new stronger types. These are mostly suggestions and can be done as a follow up or ignored.

@Ekleog-Polygon Ekleog-Polygon requested a review from iljakuklic June 5, 2025 11:49
Copy link
Contributor
@iljakuklic iljakuklic left a comment

Choose a reason for hiding this comment

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

Another pass over the strong type changes

Copy link
Contributor
@iljakuklic iljakuklic left a comment

Choose a reason for hiding this comment

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

Workflow question: How does this relate to #819? Seems a number of changes is duplicate among the two PRs. Could #819 be made target of this branch?

@Ekleog-Polygon
Copy link
Contributor Author
Ekleog-Polygon commented Jun 16, 2025

This PR actually builds on top of #819 (as per the PR description 😝). So yes, all changes from #819 are also duplicated here, it's also the reason why I've left it as draft until #819 lands and we can easily review the diff between this and main-then. This being said, thank you very much for your reviews, that are helping me start to improve on this PR even before #819 lands 😄

(As for making #819 the target of this branch, last time I tried that, when I merged the base github completely broke my PR and I had to reopen it. So I decided to just keep both targeting main, leave this one as draft, and just merge main into this branch once #819 will have merged-in; that should hopefully work fine)

@Ekleog-Polygon Ekleog-Polygon marked this pull request as ready for review June 25, 2025 16:38
@Ekleog-Polygon Ekleog-Polygon requested a review from a team as a code owner June 25, 2025 16:38
@Ekleog-Polygon Ekleog-Polygon requested a review from Freyskeyd June 25, 2025 16:38
Co-authored-by: Simon Paitrault <spaitrault@polygon.technology>
iljakuklic
iljakuklic previously approved these changes Jun 27, 2025
atanmarko
atanmarko previously approved these 10000 changes Jun 27, 2025
atanmarko
atanmarko previously approved these changes Jun 30, 2025
@Ekleog-Polygon Ekleog-Polygon added this pull request to the merge queue Jun 30, 2025
Merged via the queue into main with commit df035c8 Jun 30, 2025
25 checks passed
@Ekleog-Polygon Ekleog-Polygon deleted the ekleog/settlement-cleanup branch June 30, 2025 13:52
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.

Use strong types to semantically differentiate plain data
4 participants
0