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

Break status into execution status and finality status #107

Merged
merged 1 commit into from
Jul 9, 2023

Conversation

ArielElp
Copy link
Collaborator

@ArielElp ArielElp commented Jul 4, 2023

This change is Reviewable

@ArielElp ArielElp requested a review from EvyatarO July 4, 2023 11:55
Comment on lines +2255 to +2354
"finality_status": {
"title": "Finality status",
"type": "string",
"enum": [
"ACCEPTED_ON_L2",
"REVERTED"
"ACCEPTED_ON_L2"
],
"description": "The status of the transaction"
"description": "The finality status of the transaction"
},
Copy link
Contributor

Choose a reason for hiding this comment

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

This should be TXN_FINALITY_STATUS and not its own enum?

Copy link

@joshklop joshklop left a comment

Choose a reason for hiding this comment

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

I think the required fields for COMMON_RECEIPT_PROPTERTIES need to be updated to reflect the changes.

Copy link
Collaborator Author

@ArielElp ArielElp left a comment

Choose a reason for hiding this comment

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

correct, done

Reviewed 1 of 1 files at r1, all commit messages.
Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @EvyatarO and @Mirko-von-Leipzig)


api/starknet_api_openrpc.json line 2262 at r1 (raw file):

Previously, Mirko-von-Leipzig (Mirko von Leipzig) wrote…

This should be TXN_FINALITY_STATUS and not its own enum?

This is PENDING_RECEIPT_... so there’s only one possible option for the finality. So far, this is how we have represented "constant" fields in different objects. WDYT?

Copy link
Collaborator Author

@ArielElp ArielElp left a comment

Choose a reason for hiding this comment

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

Reviewed 1 of 1 files at r2, all commit messages.
Dismissed @Mirko-von-Leipzig from a discussion.
Reviewable status: :shipit: complete! all files reviewed, all discussions resolved (waiting on @EvyatarO)

Copy link
Collaborator

@EvyatarO EvyatarO left a comment

Choose a reason for hiding this comment

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

Reviewed 1 of 1 files at r3, all commit messages.
Reviewable status: :shipit: complete! all files reviewed, all discussions resolved (waiting on @ArielElp)

@yoga-braavos
Copy link

@ArielElp @EvyatarO , as the case with the gateway API, I suggest to keep the status for backwards compatibility reasons.

@EvyatarO
Copy link
Collaborator

EvyatarO commented Jul 6, 2023

@yoga-braavos
The feeder gateway will keep the old status field. And the RPC v0.3.0 also has it.

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