Skip to content
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

Two potential additions #33

Open
Aetherinox opened this issue Jan 20, 2024 · 0 comments
Open

Two potential additions #33

Aetherinox opened this issue Jan 20, 2024 · 0 comments

Comments

@Aetherinox
Copy link

Aetherinox commented Jan 20, 2024

If you have enough time, two proposed features would be a huge bonus to this project.

  1. No specified input folder would result in the current working directory being selected
  • Primarily this is for the --verify argument
  • You'd have to add a manual entry to the excludeSpecList list which excludes DirHash.exe
  1. Being able to specify a single filename in a manner such as
DirHash --verify "SHA256.txt" --file "somefile.zip"

and have it check the hash for the specified is in the sha256.txt file. Instead of looping through all the entries.

Not sure of what direction you want to take this app in, but I figured I would throw these out there, because these are two features that would heavily help.

Unfortunately, C and C++ are not my primary languages. I could add these to my own build, but the biggest concern would the first suggestion.

You can set the current working directory, however, that would leave argv and argc an argument short which shifts everything unless you define the current working directory and then manually insert that back into argv and argc so that it can be used further down in the code. Otherwise you end up with the algorithm Blake3 being used every time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant