-
Notifications
You must be signed in to change notification settings - Fork 19
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(golem-network): added getIdentity method to GolemNetwork object #1073
Open
mgordel
wants to merge
3
commits into
beta
Choose a base branch
from
feature/JST-1058/get-identity
base: beta
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from 2 commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We shouldn't blindly forward the data without any documentation this way. It's not clear for the user of this API what glm.getIdentity().identity means as it's
identity->identity
and there's not tsdoc that explains particular fields to the user.I've tested the code and get the following result from the
getIdentity()
:This is roughly similar to output of
yagna app-key show eth-warsaw-workshop-test --json
:I guess that the naming of things is broken on yagna's API and in fact we have a mixture of
identity
andapp-key
concepts, where an app-key belongs to anidentity
.As far as I'm aware, "identity" of the "Golem User" is established by his ETH address. This is reflected by
yagna id show
:So actually, I'd rather expect from
glm.getIdentity(): string -> "0x46b1..."
instead of the object which melts together the identity and app-key information.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, it's a bit confusing. I wanted to be consistent with yagna api. And the entity should probably contain fields:
{nodeId, name, role}
-> https://github.com/golemfactory/ya-client/blob/master/model/src/identity.rsbut for our purposes I agree that a single nodeId string might be better