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

Improve Dispute module functions #60

Merged
merged 9 commits into from
Feb 11, 2024
Merged

Improve Dispute module functions #60

merged 9 commits into from
Feb 11, 2024

Conversation

DonFungible
Copy link
Contributor

No description provided.

@DonFungible DonFungible changed the base branch from main to dev February 8, 2024 09:35
packages/core-sdk/src/resources/dispute.ts Outdated Show resolved Hide resolved
packages/core-sdk/src/resources/dispute.ts Show resolved Hide resolved
packages/core-sdk/src/resources/dispute.ts Outdated Show resolved Hide resolved
packages/core-sdk/src/abi/sdkEntities.json Outdated Show resolved Hide resolved
client.dispute.whitelistDisputeTags({
tag: "testTag",
allowed: true,
describe("[Write Functions] Should be able to", async function () {
Copy link
Contributor

Choose a reason for hiding this comment

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

All write functions are skipped right now. Are they working?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Doesn't work unless we have a working ArbitrationPolicy fixture

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Also, setDisputeJudgement won't work unless we set up the whitelisted Arbitration relayer contract (or whatever it's called)

linkToDisputeEvidence: string;
targetTag: string;
export type CancelDisputeRequest = {
disputeId: number | string | bigint;
Copy link
Contributor

Choose a reason for hiding this comment

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

I think we just use either number or string here. Otherwise users have to figure out which types to use.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I think bigint is ok here. If a user uses ethers/wagmi to read directly from the contract, that output is bigint type.

@edisonz0718 edisonz0718 merged commit 012963a into dev Feb 11, 2024
1 check passed
@DonFungible DonFungible deleted the don/improve-dispute branch October 16, 2024 02:17
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.

2 participants