-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
LEX with Content-Addressing in user's graph #1267
Comments
i thought the same but you dont necessarily need Content-Addressing in a user graph. as the content is protected by the hash. so hash it like normal. and save it like normal.. put/store the hash's "soul" in the user graph that points to the hashed content you may just want to store the |
I thought about hash it normal, but sometimes I want to edit or delete the message from my own user graph and save soul in the room (user graph). LEX is not working in user graph without hash, is it? |
https://gun.eco/docs/SEA.certify#5-there-are-ways-to-get-a-list-of-links-added-by-a-particular-user Is the code broken or outdated? |
@bmatusiak I kept testing. LEX does not work in user graph at all. How can we fix it? |
use lex in map, not in get, as per @amark |
@bmatusiak https://jsfiddle.net/c04fnro3/24/ The operator "=" does not work in user graph, only public graph. Can you test? |
Here's my fix for LEX in user graph. It works for me, I tested it in public graph, content-addressing in public graph, user graph, and user graph with cerify. The only thing is that the operator "=" does not work well with content-addressing (key + hash) in user graph and public graph. I'm sure we can fix that but for now I want LEX to work in user graph. Let me know what you think of the code below. gun.js lines 25 - 41 |
I spent more time testing with the current code in gun.js and I found that |
I have a fix for LEX issue. I ran "npm run test" and all passed. Can one of you give me an access to commit my fix and review it? |
https://gun.eco/docs/SEA.certify#5-there-are-ways-to-get-a-list-of-links-added-by-a-particular-user
// 1. We may use a LEX query to get all links for a particular user gun .user(room.pub) .get('#links') .get({'.': {'*': Bob.pub}}) .map() .once((d,k)=> { bobLinks[k]= JSON.parse(d) })
It works only without gun.user(room.pub). Is it a bug? I really want this part for my project.
The text was updated successfully, but these errors were encountered: