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

Various bits of feedback about v7 #321

Merged
merged 1 commit into from
Oct 5, 2024
Merged

Various bits of feedback about v7 #321

merged 1 commit into from
Oct 5, 2024

Conversation

robdmoore
Copy link
Contributor

  • feat: Readonly calls from app client now don't invoke signing
  • feat: AlgoKitComposer.simulate() now has a skipSignatures option to opt-out of signing for the simulate call
  • feat: Added a defaultSigner to AppClient and AppFactory
  • feat: AppClient now has an algorand property so you don't need to pass AlgorandClient around everywhere if you have a client
  • feat: AppFactory now has an algorand property so you don't need to pass AlgorandClient around everywhere if you have a factory
  • feat: AppFactory now has appName and appSpec properties so if you want this information it's exposed rather than private
  • feat: appFactory.deploy now allows you to override appName so if you want to create multiple contracts from a factory with different names you can
  • BREAKING CHANGE: AppClient.compile (and appClient.compile, and appFactory.compile) return compiledApproval and compiledClear again This reverted the last commit after a reflection that the more explicit naming was actually confusing since it meant the return of this method different from the return from create/update calls and consistency was better. The fact there is now jsdoc comments means that the property names from the compile method are able to be quickly understood.

feat: AlgoKitComposer.simulate() now has a `skipSignatures` option to opt-out of signing for the simulate call
feat: Added a `defaultSigner` to `AppClient` and `AppFactory`
feat: `AppClient` now has an `algorand` property so you don't need to pass `AlgorandClient` around everywhere if you have a client
feat: `AppFactory` now has an `algorand` property so you don't need to pass `AlgorandClient` around everywhere if you have a factory
feat: `AppFactory` now has `appName` and `appSpec` properties so if you want this information it's exposed rather than private
feat: `appFactory.deploy` now allows you to override `appName` so if you want to create multiple contracts from a factory with different names you can

BREAKING CHANGE: AppClient.compile (and appClient.compile, and appFactory.compile) return `compiledApproval` and `compiledClear` again
This reverted the last commit after a reflection that the more explicit naming was actually confusing since it meant
the return of this method different from the return from create/update calls and consistency was better. The fact there is now jsdoc
comments means that the property names from the compile method are able to be quickly understood.
@robdmoore robdmoore merged commit 9c3897e into main Oct 5, 2024
2 checks passed
@robdmoore robdmoore deleted the v7-feedback branch October 5, 2024 04:18
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.

1 participant