Skip to content
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

Feat/devx 362 abstract required bundler #341

Merged
merged 5 commits into from
Dec 23, 2023

Conversation

VGabriel45
Copy link
Collaborator

Summary

Abstracted the need for the client to create an instance of Bundler and assign it to the smart account.
Added a light way of assigning a Bundler by just providing a "bundlerUrl" param.

Change Type

  • Bug Fix
  • Refactor
  • New Feature
  • Breaking Change
  • Documentation Update
  • Performance Improvement
  • Other

Checklist

  • My code follows this project's style guidelines
  • I've reviewed my own code
  • I've added comments for any hard-to-understand areas
  • I've updated the documentation if necessary
  • My changes generate no new warnings
  • I've added tests that prove my fix is effective or my feature works
  • All unit tests pass locally with my changes
  • Any dependent changes have been merged and published

Copy link

linear bot commented Dec 22, 2023

package.json Outdated Show resolved Hide resolved
Copy link
Contributor

@AmanRaj1608 AmanRaj1608 left a comment

Choose a reason for hiding this comment

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

Need to fix merge conflicts, other than that LGTM

@livingrockrises
Copy link
Contributor

can you please resolve the conflicts

@@ -89,6 +88,14 @@ type ConditionalValidationProps = RequireAtLeastOne<
"defaultValidationModule" | "signer"
>;

type ConditionalBundlerProps = RequireAtLeastOne<
Copy link
Contributor

Choose a reason for hiding this comment

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

I see you already have conditional props. would there be a case when bundler is not used at all?
if someone is using only paymaster service for estimations and just building userops.
@AmanRaj1608

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

As we discussed yesterday, I believe bundler should be required as you cannot do much without it and it will also help us to abstract things like chain id in the future. Clients that currently create smart accounts without bundler will need to update the codebase.

Copy link
Contributor

Choose a reason for hiding this comment

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

we should mention this in the docs after release

Copy link
Contributor

@livingrockrises livingrockrises left a comment

Choose a reason for hiding this comment

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

resolve conflicts and check comments

@livingrockrises livingrockrises merged commit 7d6e68d into develop Dec 23, 2023
2 checks passed
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.

4 participants