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: handle arbitrary transaction motion #304

Merged
merged 3 commits into from
Jan 13, 2025

Conversation

Nortsova
Copy link
Contributor

@Nortsova Nortsova commented Dec 12, 2024

This PR is cover JoinColony/colonyCDapp#3536 and could be tested in scope of JoinColony/colonyCDapp#3933

@Nortsova Nortsova self-assigned this Dec 12, 2024
@Nortsova Nortsova force-pushed the feat/3536-arbitrary-motion branch 2 times, most recently from 0e26955 to e0db2b5 Compare December 16, 2024 21:20
@Nortsova Nortsova force-pushed the feat/3536-arbitrary-motion branch from e0db2b5 to de081f2 Compare December 19, 2024 15:17
Copy link
Contributor

@mmioana mmioana left a comment

Choose a reason for hiding this comment

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

Nice and simple changes @Nortsova 🙌
Tested as part of the CDapp PR

Copy link
Contributor

@bassgeta bassgeta left a 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 👌

Copy link
Contributor

@iamsamgibbs iamsamgibbs left a 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),
Copy link
Contributor

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.

Copy link
Collaborator

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.

Copy link
Collaborator

@jakubcolony jakubcolony left a 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),
Copy link
Collaborator

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,
Copy link
Collaborator

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.

@Nortsova Nortsova merged commit 16cc474 into master Jan 13, 2025
1 check passed
@Nortsova Nortsova deleted the feat/3536-arbitrary-motion branch January 13, 2025 10:11
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.

5 participants