-
Notifications
You must be signed in to change notification settings - Fork 1
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: handle arbitrary transaction motion #304
Conversation
0e26955
to
e0db2b5
Compare
e0db2b5
to
de081f2
Compare
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.
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.
Tested as part of its CDapp counterpart 👌
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.
Nice job! Reviewed alongside the CDapp counterpart.
@@ -52,7 +52,6 @@ export default async (event: ContractEvent): Promise<void> => { | |||
await writeActionFromEvent(event, colonyAddress, { | |||
type: ColonyActionType.MakeArbitraryTransaction, | |||
initiatorAddress: receipt.from, | |||
recipientAddress: receipt.to, | |||
fromDomainId: getDomainDatabaseId(colonyAddress, Id.RootDomain), |
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.
I'm not sure we actually need this as it is only possible to create arbitrary transactions in the root domain, although looking at some of the other actions we use this fromDomainId
even if can only be created in the root domain so maybe it is still required.
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.
That's a good point, there's no concept of domain when it comes to arbitrary transactions. I would opt for removing this to avoid confusion.
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.
LGTM 👍
@@ -52,7 +52,6 @@ export default async (event: ContractEvent): Promise<void> => { | |||
await writeActionFromEvent(event, colonyAddress, { | |||
type: ColonyActionType.MakeArbitraryTransaction, | |||
initiatorAddress: receipt.from, | |||
recipientAddress: receipt.to, | |||
fromDomainId: getDomainDatabaseId(colonyAddress, Id.RootDomain), |
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.
That's a good point, there's no concept of domain when it comes to arbitrary transactions. I would opt for removing this to avoid confusion.
@@ -52,7 +52,6 @@ export default async (event: ContractEvent): Promise<void> => { | |||
await writeActionFromEvent(event, colonyAddress, { | |||
type: ColonyActionType.MakeArbitraryTransaction, | |||
initiatorAddress: receipt.from, | |||
recipientAddress: receipt.to, |
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.
I see what you mean now, it makes sense to remove this as it would always point to the colony rather than the target contract address of the arbitrary transaction.
This PR is cover JoinColony/colonyCDapp#3536 and could be tested in scope of JoinColony/colonyCDapp#3933