feat: Issue 4

[zg009]

Describe your changes

Please include a summary of the change, a relevant motivation and context.
#4

Added:
-utils.go
-utils_test.go

Includes a HashEquals function which takes an input and output string and a possible user-determined crypto.Hash function (default is SHA256 according to DPoP standard) and determines equality.

Updated:
-errors.go
Utility error functions to make life easier for debugging and housekeeping

Code quality attempted to match library standard. If housekeeping is needed send back with clarifying statements

Issue ticket number and link

Attempt to fix #4 (Issue 4)

Checklist before requesting a review

• I have performed a self-review of my own code
• I have verified that the code builds perfectly fine on my local system
• I have added tests that prove my fix is effective or that my feature works
• I have commented my code, particularly in hard-to-understand areas
• I have verified that my code follows the style already available in the repository
• [?] I have made corresponding changes to the documentation

[a354dpa]

Thank you very much for your contribution!

This PR misses the mark a little bit. What we really need is to break out the actual hashing to a function that can be reused. The PR does this, but in the HashEquals method. It would be helpful if the hashing itself was to be its own method, with the equals function may still be there but make it call on the Hash-function.

[SalladinBalwer]

This is a great contribution, I still have a few comments that you can look at.

I would also like for you to change the PR title to feat: issue 4 as we use conventional commits and go-releaser to handle semantic versioning.

[SalladinBalwer]

This is almost complete, I don't have access to a computer and can't check coverage.

Just make sure that coverage is complete and we'll look at merging this.