-
Notifications
You must be signed in to change notification settings - Fork 136
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
Call #453
Merged
Call #453
Changes from 14 commits
Commits
Show all changes
18 commits
Select commit
Hold shift + click to select a range
0b6aacb
return properties for zome_info
zo-el 802db92
clean
zo-el 0c510f7
Apply suggestions from code review
maackle 0da78aa
Ignore flaky test
maackle a21ea8c
Update tests.rs
freesig e0e698e
checkpoint
neonphog 03642d1
checkpoint test harness
neonphog 1d9118e
debugging
neonphog e5f386e
cleanup
neonphog f967821
use test harness for kitsune tests
neonphog b0074f6
move init_tracing out of harness spawn
neonphog d0c2ef4
working call
freesig da56dd1
Merge branch 'develop' into call
freesig e3e5be1
pass workspace into zome call
freesig 9ee3abc
Merge branch 'develop' into call
freesig 9339d10
pr fixes, take dna hash
freesig 0db6a8f
Merge branch 'develop' into call
freesig 1af620b
add cell id to allow bridge calls in call
freesig File filter
Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1 +1,26 @@ | ||
//! @todo | ||
use crate::prelude::*; | ||
use holo_hash::AgentPubKey; | ||
use holochain_wasmer_guest::SerializedBytesError; | ||
use holochain_zome_types::{ | ||
call::Call, | ||
zome::{FunctionName, ZomeName}, | ||
}; | ||
|
||
use crate::host_fn; | ||
|
||
pub fn call( | ||
to_agent: AgentPubKey, | ||
zome_name: ZomeName, | ||
fn_name: FunctionName, | ||
cap_secret: Option<CapSecret>, | ||
request: SerializedBytes, | ||
) -> Result<ZomeCallResponse, SerializedBytesError> { | ||
freesig marked this conversation as resolved.
Show resolved
Hide resolved
|
||
let provenance = agent_info!()?.agent_latest_pubkey; | ||
host_fn!( | ||
__call, | ||
CallInput::new(Call::new( | ||
to_agent, zome_name, fn_name, cap_secret, request, provenance | ||
)), | ||
CallOutput | ||
) | ||
} |
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
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
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
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
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
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
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
Oops, something went wrong.
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.
I notice this is a function rather than a macro. Don't get me wrong -- the fewer exclamation points the better, esp for people who are using RLS for code intel -- but in order to be consistent with the other host functions, should it stay a macro for now?
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 are planning to make them all function calls very soon
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.
I'd rather just change them all to functions then add in macros to then change back. It's not a big job to change them
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.
That'd be lovely. Another thing that I've discovered in my "audit of RSM documentation" is that macros thwart rustdoc's ability to do auto-linking of argument and return types, which is painful for dev ergonomics. Means they have to do a lot of legwork themselves via the search box.