MCPcopy Create free account
hub / github.com/atomicdotdev/atomic / vault_path_for

Function vault_path_for

atomic-repository/src/intent_bridge.rs:359–367  ·  view source on GitHub ↗

Resolve the vault-relative path of a stored intent via the manifest. `vault_intent_show` normalizes and confirms existence but does not return a path; `normalize_intent_id` is private, so we match the manifest keys case-insensitively (the manifest keys are the normalized IDs, e.g. `"PIMO-1"`). Returns `None` if the intent has no manifest entry / path.

(repo: &Repository, id: &str)

Source from the content-addressed store, hash-verified

357/// case-insensitively (the manifest keys are the normalized IDs, e.g.
358/// `"PIMO-1"`). Returns `None` if the intent has no manifest entry / path.
359pub fn vault_path_for(repo: &Repository, id: &str) -> BridgeResult<Option<String>> {
360 let manifest = repo.vault_manifest()?;
361 Ok(manifest
362 .intents
363 .iter()
364 .find(|(key, _)| key.eq_ignore_ascii_case(id))
365 .map(|(_, summary)| summary.vault_path.clone())
366 .filter(|p| !p.is_empty()))
367}
368
369#[cfg(test)]
370mod tests {

Callers 2

runMethod · 0.85
stale_is_stale_and_naFunction · 0.85

Calls 4

vault_manifestMethod · 0.80
iterMethod · 0.45
cloneMethod · 0.45
is_emptyMethod · 0.45

Tested by 2

runMethod · 0.68
stale_is_stale_and_naFunction · 0.68