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

[Access] 4506 - Make CCF encoded events optional via request parameter #484

Merged

Conversation

Guitarheroua
Copy link
Collaborator

onflow/flow-go#4506

Context

This pull request introduces a new request parameter for a list of endpoints from the AccessAPI and the ExecutionDataAPI, which specifies the encoding for events.

As part of this PR:

@turbolent turbolent requested review from a team, koko1123 and peterargue and removed request for a team October 18, 2023 16:56
Copy link
Member

@turbolent turbolent left a comment

Choose a reason for hiding this comment

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

👍

adapters/access.go Show resolved Hide resolved
@peterargue
Copy link
Contributor

@Guitarheroua can you pull in master and resolve these conflicts?

Copy link
Contributor

@peterargue peterargue left a comment

Choose a reason for hiding this comment

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

looks good to me

@turbolent turbolent merged commit 0273f8f into onflow:master Oct 24, 2023
3 checks passed
@@ -190,3 +190,6 @@ require (
modernc.org/sqlite v1.21.1 // indirect
nhooyr.io/websocket v1.8.7 // indirect
)

//TODO: Remove when both version will be merged
replace github.com/onflow/flow-go v0.32.3 => github.com/Guitarheroua/flow-go v0.0.0-20231024184136-247768e776f7
Copy link
Contributor

Choose a reason for hiding this comment

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

@peterargue do you know if we can remove this statement? does flow-go has the required changes?

Copy link
Contributor

Choose a reason for hiding this comment

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

yes, though we haven't tagged a release including this yet. should be tagged later this afternoon

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.

4 participants