Skip to content

Commit

Permalink
feat: create plugin path alongside repo cache
Browse files Browse the repository at this point in the history
  • Loading branch information
patrickjcasey committed Aug 23, 2024
1 parent be480c3 commit 51e4419
Show file tree
Hide file tree
Showing 2 changed files with 5 additions and 2 deletions.
2 changes: 2 additions & 0 deletions hipcheck/src/cache.rs
Original file line number Diff line number Diff line change
Expand Up @@ -220,6 +220,8 @@ pub struct HcCache {
impl HcCache {
pub fn new(path: &Path) -> Self {
let clones_path = pathbuf![path, "clones"];
// TODO: use this path for managing/interacting with hc plugins
let _plugins_path = pathbuf![path, "plugins"];
let entries: Vec<CacheEntry> = HcCacheIterator::new(clones_path.as_path()).collect();
HcCache {
path: clones_path,
Expand Down
5 changes: 3 additions & 2 deletions site/content/docs/guide/concepts/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -64,8 +64,9 @@ priority). Each directory serves a specific purpose:
- The Config directory: stores Hipcheck's configuration files.
- The Data directory: stores Hipcheck's helper scripts needed for running
additional external tools Hipcheck relies on.
- The Cache directory: stores local clones of repositories Hipcheck is
analyzing.
- The Cache directory:
- stores local clones of repositories Hipcheck is analyzing
- stores Hipcheck plugins

Of these, the Cache directory is one that has a tendency to grow as your
use of Hipcheck continues. Some Git repositories, especially those for
Expand Down

0 comments on commit 51e4419

Please sign in to comment.