-
Notifications
You must be signed in to change notification settings - Fork 3
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
Zome/trust graph #28
Zome/trust graph #28
Conversation
let rollup = trust_atom::create( | ||
trust_atom.target_entry_hash, trust_atom.label, None, algo, trust_atoms_collection |
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.
In my reading of this we only create one TrustAtom, regardless of how many targets there are, of my atoms, and my (agent)atoms' atoms.
What we want is to end up with one rollup TrustAtom for every one of the targets of my atoms, and the targets of my (agent)atoms' atoms.
I added to the example in #25 to try to clarify:
eg : given my TAs:
me -[holochain, 0.99]-> zippy
me -[holochain, 0.80]-> robert
me -[holochain, 0.99]-> HIA
me -[engineering, 0.88]-> Telos
zippy -[holochain, 0.99]-> HIA
robert -[holochain, -0.99]-> HIA
robert -[engineering, 0.99]-> Ethereum
then rollup atoms will be:
me -[rollup, holochain, 0.98]-> HIA // actual value is TBD
me -[rollup, engineering, 0.99]-> Ethereum // actual value is TBD
me -[rollup, engineering, 0.88]-> Telos // actual value is TBD
zomes/hc_zome_trust_atom/src/lib.rs
Outdated
pub mod trust_graph; | ||
pub use crate::trust_graph::*; | ||
pub(crate) mod utils; | ||
pub(crate) mod test_helpers; |
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.
can sweetest still use this?
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.
tried using pub(super) got error: "too many leading super keywords"
going to leave it public for now
zomes/hc_zome_trust_atom/src/lib.rs
Outdated
pub content_full: Option<String>, | ||
pub content_starts_with: Option<String>, | ||
pub value_starts_with: Option<String>, | ||
} | ||
|
||
// ZOME API FUNCTIONS | ||
|
||
#[hdk_extern] | ||
pub fn create_rollup(filter: Linktag) -> ExternResult<Vec<TrustAtom>> { | ||
|
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.
todo :)
pub source_entry_hash: EntryHash, | ||
pub target_entry_hash: EntryHash, |
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.
not sure
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.
left as B64
trust graph algorithm, rollup tests one zome, trust_graph, rollup, agents Notes Notes alt strategy for agent, slver & gold rollup method alt strategy for agent, slver & gold rollup method alt strategy for agent, slver & gold rollup method Comment bin/run (cargo-release) version 0.0.6 (cargo-release) start next development iteration 0.0.7-dev Docs on latest version Remove HC patches, no longer needed Upgrade to HDK 125 / HC 130 Remove hc version from holonix (cargo-release) version 0.0.7 (cargo-release) start next development iteration 0.0.8-dev Iterate
83bac9a
to
69996b9
Compare
|
||
for agent in agents { | ||
let agent = EntryHash::from(agent); | ||
let links = get_links(agent.clone(), Some(LinkTag(filter)))?; |
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.
this should find TAs only with prefix rollup
, right?
#24 #25
fixes #29 by using fn get_latest