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

Send user extensions in request #47

Merged
merged 1 commit into from
Nov 19, 2019
Merged

Conversation

hannahhoward
Copy link
Collaborator

Goals

Allow Graphsync users to pass extensions data of their own in a Graphsync request.

Implementation

  • Add variadic args to request to allow passing an arbitrary set of extension data in a Graphsync request.
  • Pass args to request manager and into outgoing graphsync request message

add the ability to send extensions when creating requests
@hannahhoward hannahhoward changed the title feat(extensions): send extension in request Send user extensions in request Nov 18, 2019
@hannahhoward hannahhoward merged commit 5f97d3e into master Nov 19, 2019

returnedData2, found := gsr.Extension(extensionName2)
if !found || !reflect.DeepEqual(extensionData2, returnedData2) {
t.Fatal("Failed to encode first extension")

Choose a reason for hiding this comment

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

"second extension"?

@mvdan mvdan deleted the feat/send-extensions branch December 15, 2021 14:15
marten-seemann pushed a commit that referenced this pull request Mar 2, 2023
* refactor(graphsync): extract common utilities

Simplify the graphsync implementation by extracting all utilities that aren't unique to graphsync to
their own class. Also use stored counter from go-storedcounter (for persistence). Move extension
utilities to seperate file

* fix(deps): mod tidy, lint
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.

3 participants