-
Notifications
You must be signed in to change notification settings - Fork 2
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: last transaction #481
feat: last transaction #481
Conversation
…ID for contract details link
… for master safe and balance checks
…oved error handling and user feedback
Co-authored-by: Josh Miller <31908788+truemiller@users.noreply.github.com>
Co-authored-by: Josh Miller <31908788+truemiller@users.noreply.github.com>
Co-authored-by: Josh Miller <31908788+truemiller@users.noreply.github.com>
…y-xyz/olas-operate-app into mohan/refactor-onboarding
…rsonal:valory-xyz/olas-operate-app into mohan/transaction-history
@@ -76,7 +75,8 @@ export const AgentRunningButton = () => { | |||
Agent is working | |||
</Paragraph> | |||
)} | |||
<LastTransaction /> | |||
|
|||
<LastTransaction serviceConfigId={serviceConfigId} /> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is this overkill and better to extract from hook? 🤔
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fine with either approach for now, we can optimize at later point!
My preference atm is to use hooks to isolate children from parent changes where we can, though this may eventually lead to some performance issues. Yet to hit any so far however, but will memoize components/props once the time comes!
ae81ebd
into
refactor/multi-chain-support-frontend
Proposed changes
Types of changes
What types of changes does your code introduce?
Put an
x
in the boxes that apply