cxw42 / git-find Goto Github PK

In App::GitFind::Actions, add do_foo() for any or all of the following foo:

    cmin cnewer ctime
    gid group ilname iname inum ipath iregex iwholename level
    mmin mtime name
    path
    regex
    size type uid
    user wholename

In App::GitFind::Actions, implement the do_newer[aBcm][aBcmt] functions.

In App::GitFind::Actions, add function do_delete

Bonus points: add do_prune, do_quit.

Find out if the following are detailed or index tests, and implement them. Requires design discussion.

    links lname     # Actually index tests?
    perm            # Actually index test?
    ref rev         # Maybe not detailed tests - TODO investigate this
    samefile        # Actually index test?

In App::GitFind::Actions, implement do_foo() for the following foo: fls, fprint, fprint0, printf, fprintf

When searching repos (not ]]), add an entry for the commit message. Perhaps filename #, since the commit message is a comment? Permit all types of processing as if it were a real file.

E.g., skip Git::Raw::*, since the dependency on Git::Raw covers those.

In App::GitFind::Actions, add functions do_prune, do_quit. These require some design discussion first.

In App::GitFind::Actions, add functions do_empty, do_executable, do_readable, do_writeable.

Bonus points: add do_nogroup, do_nouser.

In App::GitFind::Actions, implement do_exec(), do_execdir(), do_ok(), and do_okdir().

What is the correct way to install this?

In App::GitFind::Actions, add do_foo() for any or all of the following foo:

    amin anewer atime fstype
    newer
    used

• Fast version blocked on jacquesg/p5-Git-Raw#210
• I can do a slow version by manually reading .gitmodules.

We need to be able to test operations on Git repos. Minilla might be good as a source of ideas (but not code), since it has the same need.

• Make a hierarchy under t/data that has various directories, subdirectories, ...
  • ? Add a submodule for purposes of author testing?
• Add functions to t/TestKit.pm to make it easier to run tests against the repo when checked out, and to skip those tests if we're running make test in an extracted tarball (as opposed to a clone).
• Add functional tests! E.g., does -print actually print the filenames we expect?

This is a speculative one. I don't know if this would be a good idea. However, I am intrigued by the idea of being able to use Type::Tiny's inlining system.

Ref: https://metacpan.org/pod/Type::Tiny